writing-plans

A standardized implementation plan breaks specs into bite-sized tasks covering files, tests, docs, and commits. It sequences tasks explicitly, provides file touchpoints, and ensures reproducible handoff to execution and testing phases.

Effective task breakdown generates bite-sized developer tasks covering files, tests, docs, and commits. It encourages DRY, YAGNI, and TDD principles while providing clear task sequencing and explicit file references for execution.

Yes, the implementation plan includes testing guidance and documentation steps alongside file touchpoints and commits. It generates bite-sized tasks covering tests, docs, and files while encouraging TDD principles for comprehensive delivery.

Yes, the standardized plan structure supports reproducible handoff to subagents or executing-plans workflows. It provides clear task sequencing and explicit file references necessary for automated execution by subagents.

Implementation plans are saved to docs/plans/YYYY-MM-DD-<feature-name>.md. Running the planning process in a dedicated worktree ensures the plan is automatically saved to this standardized directory structure.

A task-level breakdown is needed when starting a new feature with limited context. It provides a standardized plan structure with explicit file references, evaluation steps, and reproducible handoff to execution, testing, and documentation phases.