What problem does it solve?
writing-plans prevents costly, half-baked implementation work by forcing a clear, testable, file-by-file plan before touching non-trivial code changes.
Core Features & Use Cases
- Spec-to-Task Decomposition: Breaks a multi-step implementation into small, buildable tasks that map directly to files created or modified.
- TDD-Driven Execution Guidance: Ensures each task includes failing-test, minimal implementation, and passing-test steps with concrete commands and code.
- Safe, Context-Free Engineering Assumptions: Designs the plan as if the implementer has little or no knowledge of the codebase, reducing integration mistakes.
- Frequent Checkpoints and Commit Discipline: Encourages short step durations (2–5 minutes) and commits after completing each task.
Quick Start
Use the writing-plans skill to generate an implementation plan from your spec and save it to agents/tasks/active/<task-name>.md before starting any code changes.