writing-plans

An implementation plan transforms a feature specification into a step-by-step guide by breaking work into 2-5 minute tasks with exact file paths, failing tests first, and commit-ready sequencing for minimal ambiguity.

Task breakdown for multi-step engineering involves creating bite-sized steps with explicit file paths, exact commands, and practical review points to ensure shared context before any code is touched.

Test-driven development in implementation planning requires writing failing tests first, ensuring each 2-5 minute refactor step includes exact commands and frequent commits before sequencing the next file change.

Implementation plans apply to bug fixes and cross-file changes by providing task-by-task guidance with explicit file paths, exact commands, and commit-ready sequencing to carefully manage the workflow.

You need a rough spec or requirements list to generate an execution-ready implementation plan, which will then structure your engineering tasks into clear, actionable steps with practical review points.

You should avoid using detailed implementation plans for trivial, single-step changes that do not require task-by-task guidance, explicit file paths, or careful sequencing across multiple components.