| name | work-delegate |
| description | Work on a GitHub issue as a delegator — explore via agent, implement via a delegated executor agent (implement, test, commit, PR) |
| argument-hint | <issue-number> |
| disable-model-invocation | true |
Work on Issue (Delegated)
Implement a GitHub issue as a delegator: you orchestrate and judge; an explore agent maps the code and an executor agent reads and writes it. You do not read repo files yourself beyond the issue and the docs listed below — judge reports and plans against the issue, not against the repo.
Gated spawns (applies to both agents below). Spawn each agent with a minimal prompt: identify its role and instruct it to reply "ready" and stop, using no tools. Deliver the real task as the first SendMessage continue. Rationale: spawn-form and resume-form system prompts differ, so an agent's first continue always breaks the prompt cache; gating pays that break at ~0 context and makes every later continue (follow-ups, phase B, fix rounds) a cache hit. Cache TTL is 1h across the board, so pauses for delegator judgment or user questions under an hour don't lose the prefix. Always continue the same agent via SendMessage — never respawn (respawning loses its context and re-bills the reading).
Git state:
!git status --short; git branch --show-current; git log --oneline -5
Issue number: $ARGUMENTS
Workflow
-
Understand. gh issue view <n> --json number,title,body,labels,milestone. Briefly summarize description, acceptance criteria, and out-of-scope.
