What problem does it solve? Turning a feature specification into working code often fails because engineers (or AI agents) lack codebase context and jump into coding without a structured approach. This Skill converts a spec into a complete, step-by-step implementation plan with exact file paths, real code, test commands, and commit points, so implementation can proceed without ambiguity. ## Core Features & Use Cases - Spec-to-Plan Conversion: Transforms a requirements document into a plan saved at docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md with goal, architecture, and tech stack headers. - Fine-Grained TDD Task Breakdown: Splits work into 2-5 minute steps following the write-failing-test, verify-failure, implement, verify-pass, commit cycle, with checkbox tracking. - Placeholder-Free Enforcement and Self-Check: Forbids TODOs and vague steps, then runs a self-review for spec coverage, placeholder scanning, and type/name consistency across tasks. - Use Case: After brainstorming a new API feature, use this Skill to produce a plan where each task lists exact files to create or modify, complete test and implementation code, pytest commands with expected output, and git commit commands, ready for subagent-driven or inline execution. ## Quick Start Ask the AI to use the writing-plans skill to create an implementation plan from your feature specification document.
