writing-plans

To create a comprehensive implementation plan, define multi-step tasks with specific file touchpoints, tests, commands, and commit messages. This approach ensures repeatable execution by documenting everything an engineer needs, assuming zero codebase context, using bite-sized tasks and test-driven development principles.

The best way to break down software engineering tasks is providing a single-document, phase-based plan with clear headings. Detail required files, tests, and documentation for each bite-sized task, applying DRY, YAGNI, and TDD principles to guide engineers with zero codebase context through repeatable execution steps.

Apply test-driven development to your task breakdown by structuring the implementation plan with bite-sized tasks that include explicit testing steps. Document the required test files, commands, and validation steps for each task before writing code, ensuring frequent commits and repeatable execution across all phases.

Implementation planning works effectively for multi-phase software engineering projects by organizing tasks into a single document with a table of contents and clear phase headings. It captures precise file touchpoints, tests, documentation, and commit messages across all phases to ensure repeatable execution.

An execution plan must include precise tasks, required files, tests, commands, and commit messages to ensure repeatable execution. It should detail code, testing, and documentation checks for each bite-sized task, assuming the engineer has zero codebase context and questionable taste.

You should not use a detailed step-by-step implementation plan for trivial single-step modifications that require no task breakdown, testing, or documentation checks. The planning process targets multi-step software engineering work requiring specific file touchpoints, test-driven development, and phase-based execution to ensure repeatable results.