What problem does it solve?
Turning a feature spec into code often fails because engineers lack context on the codebase, file structure, and testing conventions. This Skill converts a spec or requirements document into a complete, step-by-step implementation plan that an engineer with zero project context can execute without getting stuck.
Core Features & Use Cases
- Bite-Sized Task Decomposition: Breaks work into 2-5 minute steps following TDD: write failing test, verify failure, implement, verify pass, commit.
- No-Placeholder Enforcement: Requires exact file paths, complete code blocks, exact commands with expected output, and bans vague steps like "add error handling".
- Self-Review and Handoff: Includes a spec-coverage and consistency self-review checklist, plus an execution handoff offering parallel or inline execution modes.
- Use Case: Given a spec for a new API endpoint, produce a plan saved to
.llm/plans/YYYY-MM-DD-feature.md with checkbox-tracked tasks covering file structure, tests, implementation code, and commit steps.
Quick Start
Ask the agent to use the writing-plans skill to create an implementation plan from your feature spec before writing any code.