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, bite-sized task breakdown that an engineer (or subagent) with zero project context can execute directly. ## Core Features & Use Cases - Structured Plan Documents: Generates plans with a mandatory header (goal, architecture, tech stack, spec reference, global constraints) saved to docs/superpowers/plans/. - 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, implement, verify, commit cycle. - Placeholder Prevention & Self-Review: Enforces a no-placeholder policy (no TODOs or vague steps) and runs a self-review checklist for spec coverage, placeholder scans, and type consistency. - Execution Handoff: Offers subagent-driven or inline execution paths, with a reviewer prompt template for dispatching a plan-review subagent. - Use Case: After brainstorming a feature spec, invoke this Skill to produce a dated plan file with checkbox-tracked tasks that a fresh subagent can implement one by one. ## Quick Start Ask the agent to use the writing-plans skill to create an implementation plan from your spec document before writing any code.
