Menu
Interactive /gobby dev launcher. Dispatches the shared developer agent for a task.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | dev |
| description | Interactive /gobby dev launcher. Dispatches the shared developer agent for a task. |
| version | 1.0.0 |
| category | core |
| triggers | dev, gobby dev, developer agent, implement task |
| metadata | {"gobby":{"audience":"interactive","depth":0}} |
Use this skill when the user invokes /gobby dev to run the same developer
agent that lifecycle dispatch uses, independent of gobby build.
The workflow definition is src/gobby/install/shared/workflows/dev.yaml.
Resolve a task ref before dispatch. Accept #N, a numeric ref, or a dotted
task path. If the user does not provide one, ask for the task ref.
Ask for the I/D mode unless it is already clear from the user's request:
I) Interactive - dispatch the developer agent and surface the run ids.
D) Delegated - dispatch the developer agent and end the turn.
Persist the choice as value="interactive" | "delegated" for the handoff.
Both modes use the developer agent and the shared workflow YAML; the only
difference is whether the current session stays available for follow-up.
Run the dev workflow with the resolved task id:
call_tool("gobby-workflows", "run_pipeline", {
"name": "dev",
"inputs": {
"task_id": "<task_ref>",
"mode": "<interactive|delegated>"
}
})
Surface the returned execution id. The spawned developer agent owns the
implementation loop: claim the task, implement, validate, commit, and either
close or hand off for QA according to its agent contract.
gobby build; this is the per-task developer loop.developer agent instructions here.