What problem does it solve? Turning a feature spec into code without a plan leads to missed requirements, inconsistent types across tasks, and vague steps that stall implementation. This Skill converts a spec or requirements document into a complete, bite-sized 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 following the failing-test, implement, verify, commit cycle. - Placeholder-Free Enforcement: Forbids TODOs and vague steps, requiring actual code blocks in every step, plus a self-review pass for spec coverage, placeholders, and type consistency. - Execution Handoff: Offers subagent-driven or inline execution after the plan is saved, with a reviewer prompt template for validating the finished plan. - Use Case: Given a spec for a new workout logging feature, produce a plan where each task lists exact files to create or modify, the test code to write first, the minimal implementation, run commands with expected output, and a commit step. ## Quick Start Ask the agent to use the writing-plans skill to create an implementation plan from your spec document before writing any code.
