What problem does it solve? Engineers often start coding from a spec without a clear roadmap, leading to missed requirements, vague tasks, and inconsistent execution. This Skill turns a spec or requirements document into a complete, step-by-step implementation plan that an engineer with zero codebase context can follow. ## Core Features & Use Cases - Bite-Sized Task Decomposition: Breaks work into 2-5 minute steps following TDD: write failing test, verify failure, implement, verify pass, commit. - No-Placeholder Enforcement: Requires exact file paths, complete code blocks, exact commands with expected output, and bans vague steps like "add error handling". - Self-Review Checklist: Validates spec coverage, scans for placeholder patterns, and checks type/name consistency across tasks before handoff. - Execution Handoff: Offers subagent-driven or inline execution paths after saving the plan to docs/superpowers/plans/. - Use Case: After brainstorming a new feature spec, use this Skill to produce a dated plan document with checkbox-tracked tasks that a subagent or junior engineer can implement independently. ## Quick Start Use the writing-plans skill to create an implementation plan from my feature spec before writing any code.