What problem does it solve? Turning a spec or requirements document into an actionable implementation plan is error-prone: tasks end up too vague, placeholders slip in, and engineers without codebase context get stuck. This Skill produces a complete, self-contained plan that an engineer with zero project context can execute task by task. ## Core Features & Use Cases - Structured Plan Generation: Produces a plan document with a mandatory header (goal, architecture, tech stack, spec reference, global constraints) saved to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md. - Bite-Sized TDD Tasks: Decomposes work into tasks with exact file paths, interface contracts (consumes/produces), and 2-5 minute steps following the write-failing-test, run, implement, verify, commit cycle. - Quality Gates: Enforces a no-placeholders policy, a self-review checklist (spec coverage, placeholder scan, type consistency), and an optional plan document reviewer subagent prompt template. - Use Case: Given a feature spec for a new API endpoint, generate a plan where each task lists exact files to create or modify, real test code, run commands with expected output, and commit commands, then hand off to subagent-driven or inline execution. ## Quick Start Use the writing-plans skill to turn my spec into a step-by-step implementation plan with TDD tasks.
