What problem does it solve? Turning a spec or requirements document into working code often fails because engineers jump in without a structured plan, producing vague tasks, missing requirements, and inconsistent interfaces. This Skill converts a spec into a complete implementation plan with exact file paths, test code, and commit steps that an engineer with zero codebase context can follow. ## Core Features & Use Cases - Spec-to-Plan Conversion: Transforms requirements into a structured plan with a mandatory header, global constraints, and per-task file/interface declarations. - Bite-Sized TDD Tasks: Breaks work into 2-5 minute steps following the failing-test, implement, pass, commit cycle, with no placeholders allowed. - Self-Review and Handoff: Runs a spec-coverage, placeholder, and type-consistency check, then offers subagent-driven or inline execution. - Use Case: Given a feature spec for a new API endpoint, produce a plan saved to docs/superpowers/plans/ that lists every file to create or modify, exact test code, run commands, and commit messages for each task. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan from your spec document before writing any code.
