What problem does it solve? Turning an approved specification into work that engineers or agents can execute often fails because plans invent design, leave placeholders, or skip verification. This Skill converts approved scope into an ordered, dependency-aware implementation plan with exact files, symbols, commands, and exit criteria so execution requires no further design decisions. ## Core Features & Use Cases - Implementation Decomposition: Maps every spec requirement to bounded tasks with dependency order, execution approach (inline sequential, subagent-ready, or parallel-capable), and coordination mode (none or git-tracked). - Task Contracts: Writes per-task contracts covering purpose, required skills, files and symbols, dependencies, authority, steps, verification, and exit criteria, with executor and template profile resolution rules. - Verification Design: Defines task-local and final proof strategies, including regression, backend boundary, performance, and rollback evidence, plus a one-pass self-review for spec coverage and placeholder removal. - Use Case: After a specification for a cross-boundary feature is approved, use this Skill to produce a canonical plan at docs/superpowers/plans/ with ordered tasks, shared-write ownership, and proof commands ready for handoff to execution. ## Quick Start Use the skill-writing-plans skill to turn the approved specification into an executable implementation plan with ordered tasks and verification steps.
