What problem does it solve? Engineers often start coding from a spec without a concrete plan, leading to missed requirements, inconsistent types across tasks, and vague steps that stall implementation. This Skill turns a spec or requirements document into a complete, executable 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 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-placeholder policy, a self-review checklist (spec coverage, placeholder scan, type consistency), and an optional plan document reviewer subagent prompt. - Use Case: Given a spec for a new trip-itinerary feature, produce 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 Ask the AI to use the writing-plans skill to create an implementation plan from your spec document before writing any code.
