Menu
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.
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
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 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.
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.
| name | executing-plans |
| version | 6.2.0 |
| category | workflow |
| description | 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. |
Execute the plan in the current agent by default.
Read ../using-superpowers/references/risk-policy.md.
Do not switch to subagent-driven development merely because subagents exist. Delegate only when the user requests it or tasks are independent enough to benefit from parallel work.
Stop when authority is missing, a destructive action is newly required, a critical requirement is ambiguous, or repeated evidence invalidates the plan. Ordinary implementation details are resolved from the codebase.
When implementation is verified, use
superpowers:finishing-a-development-branch only if an integration decision is
actually needed.
