What problem does it solve? Multi-step engineering work often starts coding before goals, dependencies, risks, and acceptance evidence are clear, leading to rework and missed requirements. This Skill turns an approved spec or requirements into a durable, file-backed implementation plan that a capable engineer can execute without rediscovering context. ## Core Features & Use Cases - Outcome-Oriented Plan Structure: Captures the approved goal, ideal end state, dependencies, interfaces, risks, assumptions, and acceptance evidence without prescribing rigid steps or commits. - Wave and Task Decomposition: Organizes work into dependency-ordered waves with observable end states and useful verification evidence for each. - Optional Evidence-Driven Review: Includes a plan-document reviewer prompt template for independent scrutiny when cross-module, security, or migration risk justifies it. - Use Case: Given an approved design for a multi-module migration, produce a plan saved to docs/superpowers/plans/ that defines waves, interfaces, risks, and acceptance evidence, then hand it off to executors or subagents. ## Quick Start Ask the agent to write an implementation plan for your approved spec before touching any code.
