Menu
Use when an approved change spans multiple dependent outcomes and needs a durable implementation sequence before coding. Do NOT use for small, obvious, reversible edits.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | writing-plans |
| version | 6.2.0 |
| category | workflow |
| description | Use when an approved change spans multiple dependent outcomes and needs a durable implementation sequence before coding. Do NOT use for small, obvious, reversible edits. |
Write plans that preserve decisions and dependencies without expanding every edit into a ceremony.
Read ../using-superpowers/references/risk-policy.md.
Create a plan for multi-component work, migrations, public contracts, risky rollouts, or work likely to continue across sessions. Skip it for a straightforward change that fits in a short active checklist.
Save durable plans to the project convention, otherwise
docs/superpowers/plans/YYYY-MM-DD-<topic>.md.
Include:
Do not include placeholder steps, invented APIs, repeated prose, routine shell commands, or a commit after every tiny action. Include code only where an exact contract or non-obvious algorithm must be preserved.
Inline execution is the default. Use superpowers:subagent-driven-development
only when delegation was requested or tasks are genuinely independent.
