Menu
Use when the user requests delegated implementation or multiple substantial tasks are genuinely independent without shared state. Do NOT use for coupled or ordinary single-task work.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | subagent-driven-development |
| version | 6.2.0 |
| category | workflow |
| description | Use when the user requests delegated implementation or multiple substantial tasks are genuinely independent without shared state. Do NOT use for coupled or ordinary single-task work. |
Subagents are for isolation and parallelism. They are not the default unit of work and do not imply a reviewer after every task.
Read ../using-superpowers/references/risk-policy.md.
Stay inline when tasks share files, depend on sequential discoveries, are small, or the current agent can finish faster than briefing and integrating delegates.
Use implementer-prompt.md when a written brief helps.
superpowers:requesting-code-review.Stop delegation when tasks cease to be independent, agents edit overlapping state, or coordination costs exceed the remaining implementation work.
Use when a request leaves material product, architecture, behavior, or scope decisions unresolved. Do NOT use for approved, well-bounded implementation work.
Use when 2 or more substantial tasks are independent, have disjoint state, and parallel execution will save meaningful time. Do NOT use for coupled or sequential work.
Use when implementing an approved written plan with dependent tasks in the current session. Do NOT use when the plan is missing, unapproved, or naturally parallel.
Use when verified implementation is ready and the user must choose whether to keep, merge, or publish the branch. Do NOT use before applicable checks pass.
Use when receiving code review feedback that may be unclear or technically questionable and needs verification. Do NOT use for an unrequested general code review.
Use when a completed change is high-risk, crosses subsystem boundaries, or the user explicitly requests independent review. Do NOT use by default for low- or medium-risk changes.