What problem does it solve? Turning a feature spec into code without a plan leads to missed requirements, inconsistent types across tasks, and vague steps that stall implementation. This Skill converts a spec or requirements document into a complete, bite-sized implementation plan that an engineer with zero codebase context can execute task by task. ## Core Features & Use Cases - Structured Plan Generation: Produces a plan document with a required header, global constraints, file structure mapping, and tasks broken into 2-5 minute steps following TDD (failing test, run, implement, verify, commit). - Quality Enforcement: Bans placeholders like TODO or "add error handling", requires exact file paths and complete code in every step, and includes a self-review checklist for spec coverage, placeholder scans, and type consistency. - Execution Handoff: Saves plans to docs/superpowers/plans/ and offers subagent-driven or inline execution, plus a reviewer prompt template for dispatching a plan review subagent. - Use Case: Given a spec for a new API endpoint, produce a dated plan file where each task lists exact files to create or modify, interface signatures consumed and produced, and runnable test commands with expected output. ## Quick Start Ask the agent to use the writing-plans skill to turn your feature spec into a step-by-step TDD implementation plan saved under docs/superpowers/plans/.
