/gobby workflows - Workflow Management Skill

This skill manages step-based workflows via the gobby-workflows MCP server. Parse the user's input to determine which subcommand to execute.

Session Context

IMPORTANT: Use the session_id from your SessionStart hook context (injected at session start) for all workflow calls.

Look for Gobby Session Ref: or Gobby Session ID: in your system context:

Gobby Session Ref: #5
Gobby Session ID: <uuid>

Note: All session_id parameters accept #N, N, UUID, or prefix formats.

Do NOT call list_sessions to look it up - you already have it.

Tool Schema Reminder

First time calling a tool this session? Use get_tool_schema(server_name, tool_name) before call_tool to get correct parameters. Schemas are cached per session—no need to refetch.

Subcommands

/gobby workflows activate <workflow-name> - Activate a workflow

Call activate_workflow with:

• session_id: Required - from your SessionStart context
• name: The workflow name to activate
• variables: Optional initial variables (e.g., session_task for auto-task)
• initial_step: Optional starting step (defaults to first step)

Available workflows:

• auto-task - Task execution with session_task variable
• plan-execute - Planning then execution phases
• test-driven - TDD: Red → Green → Refactor
• plan-act-reflect - Structured development cycle
• react - Reason-Act continuous loop

Example: /gobby workflows activate plan-execute → activate_workflow(session_id="<from context>", name="plan-execute")

Example: /gobby workflows activate auto-task session_task=gt-abc123 → activate_workflow(session_id="<from context>", name="auto-task", variables={"session_task": "gt-abc123"})

/gobby workflows deactivate - Deactivate current workflow

Call end_workflow with:

• session_id: Required - from your SessionStart context

Example: /gobby workflows deactivate → end_workflow(session_id="<from context>")

/gobby workflows status - Show current workflow status

Call get_workflow_status with:

• session_id: Required - from your SessionStart context

Returns:

• Active workflow name (if any)
• Current step
• Available transitions
• Session variables

Example: /gobby workflows status → get_workflow_status(session_id="<from context>")

/gobby workflows list - List available workflows

Call list_workflows to see all available workflows:

• Built-in workflows (global)
• Project-specific workflows (.gobby/workflows/)
• Workflow descriptions and step counts

Example: /gobby workflows list → list_workflows()

/gobby workflows evaluate <workflow-name> - Dry-run workflow validation

Call evaluate_workflow to validate a workflow definition without executing. Checks structure, step reachability, transitions, and tool references.

Parameters:

• name: (required) Workflow name to evaluate
• project_path: Optional project path for lookup

Returns a WorkflowEvaluation with valid (bool), items (list of findings), and step_trace (reachability analysis).

Example: /gobby workflows evaluate auto-task → evaluate_workflow(name="auto-task")

Response Format

After executing the appropriate MCP tool, present the results clearly:

• For activate: Confirm activation with workflow name and starting step
• For deactivate: Confirm deactivation
• For status: Show current state, step, and available actions
• For list: Display workflows with name, description, and type (step/stepped)

Workflow Concepts

• Steps: Named states with allowed tools and transitions
• Variables: Session-scoped key-value storage (e.g., session_task)
• Transitions: Move between steps based on conditions
• Tool filtering: Each step restricts which tools are available

Step Transitions

Transitions between steps can be automatic or manual:

Automatic Transitions

Most workflows use condition-based transitions that fire automatically:

• step_action_count >= N - after N tool calls in the step
• task_tree_complete(...) - when tasks are done
• Variable comparisons - when workflow state changes

You don't need to manually transition - just perform the required actions and the workflow engine handles the rest.

Manual Transitions

If you need to force a transition, use request_step_transition:

call_tool("gobby-workflows", "request_step_transition", {
    "session_id": "<from context>",
    "to_step": "work",
    "reason": "Research complete, ready to implement"
})

Only use manual transitions when automatic conditions aren't met and you have justification.

Common mistake: Guessing tool names like transition_step or step_transition. The actual tool is request_step_transition.

Error Handling

If the subcommand is not recognized, show available subcommands:

• activate, deactivate, status, list, evaluate