writing-plans

This skill converts a spec into a complete end-to-end implementation plan by mapping required files, tests, and validation steps to bite-sized sequential tasks. It assumes zero codebase context and outlines commit milestones for clear execution.

Documenting an implementation plan for zero-context engineers requires detailing every required file change, test, and validation step in sequence. This breaks down the work into bite-sized, executable tasks with clear verification and commit milestones.

Mapping development tasks to specific files and validation steps involves generating a comprehensive plan from your spec that outlines each required change. This plan defines how to verify each step and establishes commit milestones to track progress sequentially.

Yes, you can hand off implementation plan execution to subagents. The generated plan explicitly outlines how to hand off execution, ensuring that bite-sized tasks mapped to specific files and tests can be delegated and validated sequentially.

Yes, this planning approach supports test-driven development workflows by mapping tasks to specific tests and validation steps. It outlines how to verify each step sequentially, ensuring tests are integrated into the commit milestones.