What problem does it solve? Engineers often start coding from a spec without a concrete plan, leading to missed requirements, vague tasks, and inconsistent implementations. This Skill turns a spec or requirements document into a complete, bite-sized implementation plan that an engineer with zero codebase context can follow task by task. ## Core Features & Use Cases - Structured Plan Generation: Produces a plan document with goal, architecture, tech stack, global constraints, and per-task file lists, interfaces, and checkbox steps. - TDD Task Decomposition: Breaks work into right-sized tasks where each step is a 2-5 minute action: write failing test, verify failure, implement, verify pass, commit. - Placeholder-Free Enforcement: Forbids TODOs and vague steps, requiring exact file paths, complete code blocks, and exact commands with expected output. - Self-Review and Handoff: Includes a spec-coverage, placeholder, and type-consistency self-review, plus an execution handoff to subagent-driven or inline execution workflows. - Use Case: Given a feature spec for a new API endpoint, produce a dated plan file in docs/superpowers/plans/ with tasks covering tests, implementation, and commits, ready for an executor agent. ## Quick Start Ask the agent to use the writing-plans skill to create an implementation plan from your spec before writing any code.
