dispatching-subagents
Turn a groomed tracker issue into a running implementation sub-agent and a merged PR — issue selection (priority, file-disjointness, bundling), model/effort resolution from chat > labels > defaults, the eight-section dispatch brief (worktree, toolchain prefix, pre-push hygiene, scope, git discipline, PR procedure, return contract), parallel dispatch under a concurrency cap, stalled-agent worktree salvage, and verify-then-trust completion checks. Use whenever you are about to spawn a sub-agent (Agent/Task tool call) to implement, fix, refactor, test, or otherwise write code from a tracker issue — even if the user only says "work the next issues", "fix these bugs", "run the loop", or "send an agent at #N" without saying "dispatch"; also use when a dispatched agent stalls, is watchdog-killed, returns status:failed, or reports completion and you must decide whether to salvage its worktree, re-dispatch, or verify its PR.
Pinned to revision 6b9d66f636cc, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.