What problem does it solve? Engineers often start coding from a spec without a clear roadmap, leading to missed requirements, inconsistent structure, and rework. This Skill turns a spec or requirements document into a complete, bite-sized implementation plan that an engineer with zero codebase context can follow. ## Core Features & Use Cases - Structured Plan Generation: Produces a plan document with a required header, file structure mapping, and tasks broken into 2-5 minute steps following TDD (failing test, run, implement, verify, commit). - Quality Guardrails: Enforces exact file paths, complete code in every step, exact commands with expected output, and bans placeholders like TODO or "add error handling". - Self-Review and Handoff: Includes a self-review checklist for spec coverage, placeholder scans, and type consistency, plus an execution handoff offering subagent-driven or inline execution. - Use Case: Given a feature spec for a new API endpoint, generate a dated plan file in docs/superpowers/plans/ with checkbox-tracked tasks that a subagent can execute one by one. ## Quick Start Ask the agent to use the writing-plans skill to create an implementation plan from your spec document before writing any code.
