Writing Plans produces the plan that execution skills follow. It maps the file structure first, splits work into tasks sized around a test cycle and a reviewer’s gate, and writes steps that each carry exactly what an implementer cannot decide alone: file paths, signatures, spec values, failing tests and the commands that prove them.
What You Get
- A plan saved under docs/superpowers/plans
- A header with goal, architecture, spec link, global constraints and review focus
- Tasks with files, interfaces and test-first steps ending in a commit
- A five-point self-review
- A handoff that recommends an execution method with one reason
Common Use Cases
- Planning a multi-step feature from an approved design
- Splitting a large spec into separate plans per subsystem
- Preparing work for a cheaper model to execute
What Makes It Unique
A plan is the set of decisions the implementer cannot make alone. The skill says a step is done when the implementer can write exactly one reasonable thing from it, warns that a plan longer than the code is a transcript, and adds a review focus list of failure modes the tests would otherwise miss.
Under The Hood
Instructions only. The agent reads the spec, writes a markdown plan file into your repository and links it for review. The skill ships no scripts and calls no outside services. It names the two execution skills it hands off to.