What problem does it solve? Turning a feature spec into code without a plan leads to missed requirements, inconsistent types, and vague tasks that stall implementers. This Skill converts a spec into a complete, self-contained implementation plan that an engineer with zero codebase context can execute task by task. ## Core Features & Use Cases - Structured Plan Documents: Produces plans 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: Breaks work into tasks with exact file paths, interface contracts (consumes/produces), and 2-5 minute steps covering failing test, verification, minimal implementation, and commit. - Self-Review and Handoff: Runs a spec-coverage, placeholder, and type-consistency check, then offers subagent-driven or inline execution of the finished plan. - Use Case: Given a 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. ## Quick Start Use the writing-plans skill to turn my feature spec into a step-by-step implementation plan with TDD tasks.