writing-plans

To break down a complex software feature, you generate a structured implementation plan that converts it into bite-sized tasks (2-5 minutes of focused work) with explicit file paths, complete code examples, and verification steps.

TDD-based task breakdown is an implementation planning approach that enforces Test-Driven Development, DRY, and YAGNI principles to keep plans minimal and reliable by specifying exact files to modify, tests to write, and clear acceptance criteria.

You create an implementation plan for cross-team handoffs by defining clear task boundaries, deliverables, file touchpoints, and verification steps, allowing subagents or teammates to execute feature work with confidence.

Yes, implementation planning applies to software features, design deltas, and code generation by providing exact file paths, complete code examples, explicit commands, and documentation integrated into the plan.

The best way to document file touchpoints and tests is to create a structured, task-by-task plan that explicitly specifies files to modify, create, and test, plus verification steps for each bite-sized task.

You should use a structured plan because writing precise, executable implementation plans is hard when context is scarce, and a structured approach provides clear task boundaries, testing commands, and documentation so teams can execute with confidence.