What problem does it solve? Turning a spec or requirements document into an executable implementation plan is error-prone: tasks end up too vague, placeholders slip in, and engineers (or subagents) with zero codebase context get stuck. This Skill produces a complete, self-contained plan where every task has exact file paths, real code snippets, test commands, and commit steps. ## Core Features & Use Cases - Bite-Sized Task Decomposition: Breaks work into tasks with 2-5 minute steps following a TDD cycle (failing test, minimal implementation, verification, commit). - Deviation Protocol: Instructs executors to stop and report when reality diverges from the plan instead of improvising fixes, preventing compounding rework. - No-Placeholder Enforcement & Self-Review: Bans TODOs and vague steps, then runs a checklist for spec coverage, placeholder scans, and type consistency across tasks. - Use Case: After brainstorming a new feature, feed the approved spec to this Skill to produce a dated plan document in docs/superpowers/plans/, ready for subagent-driven or inline execution. ## Quick Start Use the writing-plans skill to turn this feature spec into a step-by-step implementation plan with tests and commits.
