writing-plans

You break down complex software features by generating a structured implementation plan that decomposes high-level requirements into bite-sized, 2-5 minute tasks with specific file paths, TDD guidance, and clear acceptance criteria.

The best way to write an implementation plan for cross-team handoffs is to use a standardized header and per-task format that details required files, code examples, and verification steps to ensure reliable delivery with zero assumed context.

TDD guidance integrates into a task-based implementation plan by embedding testing commands and verification steps directly within each bite-sized task, ensuring development follows test-driven design principles while maintaining momentum.

Yes, you can use standardized commit conventions within a stepwise task breakdown workflow. The plan structure supports clear commit histories for traceability, enabling multi-step feature delegation and execution handoffs across teams.

You need to generate a structured implementation plan when working on complex features requiring stepwise decomposition, cross-team collaboration, or subagent delegation, ensuring every task has complete code examples and documentation references.

Implementation plan generation requires defined high-level features to decompose into actionable steps. Without clear feature definitions, the plan cannot establish the necessary task structure, file-path specificity, and acceptance criteria for reliable delivery.