What problem does it solve? Turning a feature spec into code without a plan leads to missed requirements, inconsistent types, and vague tasks that stall implementers. This Skill converts a spec into a complete, self-contained 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 interface signatures per task, and includes a self-review checklist for spec coverage and type consistency. - Execution Handoff: Saves plans to docs/superpowers/plans/ and offers subagent-driven or inline execution, with a reviewer prompt template for validating the finished plan. - Use Case: Given a spec for a new API endpoint, produce a plan where each task lists exact files to create or modify, the test code to write, the commands to run, and the commit message to use. ## Quick Start Use the writing-plans skill to turn my feature spec into a step-by-step implementation plan with TDD tasks.
