Menü
Use when the user asks to expand a task into a concrete task tree.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Instructions for using gcode CLI for code search and retrieval. Loaded on demand when project has a code index.
Pre-transition checklist for closing or reviewing tasks. Covers fresh verification evidence, commits, and memory gates.
Use when processing CodeRabbit review comments, CodeRabbit CLI reports, or `$gobby coderabbit [findings]` requests.
Use when creating, editing, or validating Gobby skills, especially when a skill must change agent behavior or become discoverable through gobby-skills.
Use when coordinating a full gobby build run for an epic or task, especially when the user assigns the current session as coordinator, asks for a coordination epic, wants build agents/worktrees monitored, or wants gobby build bugs fixed so future runs work unattended.
Router contract for provider-aware Gobby help and installed skill dispatch.
| name | expand |
| description | Use when the user asks to expand a task into a concrete task tree. |
| category | core |
| triggers | expand task, break down, subtask, decompose |
| metadata | {"gobby":{"audience":"interactive","depth":0}} |
Thin wrapper over the expand-task pipeline and the new expansion-run MCP tools.
Expansion consumes typed plans authored under the Plan-Coverage Contract in
src/gobby/install/shared/skills/plan-draft/SKILL.md; the single-page
reference is docs/contracts/plan-coverage.md.
Expansion-side obligations:
.coverage-ledger.yaml companion file MUST exist before expansion
proceeds for new epic plans.covers:<plan-id>:<section-id>:<item-id> labels for the acceptance items
they implement.expansion-qa is the mechanical gate that compares the expanded task tree
against the compiled contract and records any missing or invalid coverage.plan-ref: labels are not honored.#N or another task refpath/to/plan.md together with a target taskexpand-task pipeline with:call_tool("gobby-workflows", "run_pipeline", {
"name": "expand-task",
"inputs": {
"task_id": "<task_ref>",
"plan_file": "<optional relative plan path>"
}
})
execution_id and end the turn. The daemon sends a
durable completion notification and wake signal when the pipeline finishes.
On wake/resume, inspect the run with:call_tool("gobby-workflows", "get_pipeline_status", {
"execution_id": "<execution_id>"
})
expansion_runs, not on the task record.gobby-tasks-ops:get_latest_expansion_run or get_expansion_run for inspection.