parallel-subagent-implementationlisted

# parallel-subagent-implementation The default is **one thing at a time**. Fanning out is the authorized exception, and it relaxes no other rule. ## Route first — which fan-out is this? Read the row that matches the work in front of you and go there. Coming back here for the lane-and-gatekeeper protocol is expected; every row below depends on it. | The work | Skill | |---|---| | Independent **tickets**, disjoint lanes, all blockers met | **this skill** | | An authorized ticket **range with a dependency graph** | `subagent-batch-implementation` (waves) | | Tasks from a **written plan**, no tracker involved | `superpowers:subagent-driven-development` | | Independent **investigations** — several unrelated failures, no code to land yet | `superpowers:dispatching-parallel-agents` | | Workers sharing one checkout — briefs, timeouts, dirty trees | `shared-worktree-delegation` | | Another agent or human is writing the same tree | `shared-worktree-safety` | The plugin skills in that table cover **discovery and plan execution**; they do not know about tickets, gates, or the GitHub Project. When their output has to land as committed work on the board, the parent still runs Steps 1–6 below. ## Depth 1 — the parent fans out, workers never do A **stage parent** is a separately launched top-level session. It may dispatch one level of workers. A worker may not dispatch anything: every brief must say so in words, because a worker that re-delegates puts a claim two hops from the evidenc