writing-plans

To turn a spec into an implementation plan, you structure requirements into bite-sized tasks with file paths, tests, and documentation references. This skill converts written specifications into detailed, executable plans saved as plan.md files.

A test-driven implementation plan emphasizes test-driven steps and frequent commits to guide development from task discovery to validation. It ensures every bite-sized task includes specific test references and file paths before coding begins.

To generate a design doc plan for a new feature, you convert requirements into a structured plan saved under docs/design/{feature-name}/plan.md. This creates documentation scaffolding that includes an agent-facing specification with comprehensive task breakdowns.

The spec-to-plan workflow uses a dedicated worktree workflow to encourage frequent commits and traceable changes. This worktree setup ensures that implementation plans integrate cleanly with your existing development environment.

Yes, you can use this for multi-step software engineering tasks requiring structured task breakdowns and comprehensive design documentation before coding. It is applicable to any project needing detailed, executable implementation plans from written specifications.

You should not use an automated task breakdown approach for simple, single-step tasks that require no written specification or design documentation beforehand. It is specifically built for multi-step projects needing test-driven steps and comprehensive design docs.