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, minimal implementation, commit). - Placeholder Prevention: Enforces exact file paths, complete code blocks, and exact commands with expected output, banning TODOs and vague instructions. - Self-Review and Handoff: Runs a spec-coverage, placeholder, and type-consistency checklist, then offers subagent-driven or inline execution of the saved plan. - Use Case: Given a spec for a new API endpoint, generate a dated plan file in docs/superpowers/plans/ with checkboxed tasks covering tests, implementation, and commits, ready for task-by-task execution. ## Quick Start Use the writing-plans skill to turn this feature spec into a step-by-step TDD implementation plan saved under docs/superpowers/plans/.
