What problem does it solve? Turning a spec or requirements document into an actionable implementation plan is error-prone: engineers miss requirements, write vague tasks, or produce plans with placeholders that stall execution. This Skill converts a spec into a complete, bite-sized task plan that an engineer with zero codebase context can execute task by task. ## Core Features & Use Cases - Structured Plan Format: Enforces a mandatory plan header (goal, architecture, tech stack, global constraints) plus per-task blocks listing exact files to create or modify, interfaces consumed and produced, and checkbox steps. - TDD Bite-Sized Steps: Each task is broken into 2-5 minute steps following a test-driven cycle: write the failing test, verify it fails, implement minimal code, verify it passes, commit. - No-Placeholder Enforcement & Self-Review: Bans vague steps like "add error handling" and includes a self-review checklist covering spec coverage, placeholder scans, and type consistency across tasks. - Use Case: Given a feature spec for a new checkout flow, produce a dated Markdown plan in docs/superpowers/plans/ with exact file paths, complete code snippets, test commands with expected output, and commit messages for every task. ## Quick Start Ask the agent to use the writing-plans skill to turn your spec document into a step-by-step implementation plan saved as a dated Markdown file.
