writing-plans

An implementation plan converts a specification into file-by-file task decomposition with actionable steps and test commands. It breaks a feature into focused file-level tasks with clear responsibilities, paired with test-first steps and commit guidance.

Task decomposition splits multi-step software features into focused file-level tasks with clear responsibilities. Each task includes actionable test-first steps, exact commands, and commit guidance, ensuring an engineer can follow the plan without prior context.

Break down a feature request by pairing each file-level task with actionable test-first steps and exact test commands. This approach ensures test-driven development by requiring concrete test commands and commit guidance for every task in the implementation plan.

No, an engineer-ready implementation plan requires exact file paths. The plan needs actionable steps, concrete test commands, and self-review for completeness, consistency, and placeholder-free planning to ensure an engineer can execute it without needing prior context.

Use a self-review process for completeness, consistency, and placeholder-free planning. This catches missing requirements, placeholders, and type mismatches before handoff, ensuring the final implementation plan is fully actionable and engineer-ready.

Yes, implementation planning applies to multi-step software tasks and supports specifications needing file-by-file decomposition. It accommodates worktree setups by providing focused file-level tasks with test-first task breakdown and commit guidance.