writing-plans

Implementation planning drafts comprehensive task breakdowns when a spec exists but code is not yet written. It creates bite-sized tasks identifying files to touch, tests to write, and documentation to check before actual coding begins.

Draft a plan using a dedicated worktree by breaking the feature into bite-sized tasks with explicit files to touch, tests to write, and docs to check. Save the plan to docs/plans/YYYY-MM-DD-<feature-name>.md with a standard header and task structure.

You need an implementation plan when a spec exists but code is not yet written, especially for multi-step tasks requiring cross-team collaboration, clear execution handoff to sub-skills, or parallel execution workflows.

Yes, implementation planning integrates with TDD by identifying tests to write for each bite-sized task, and uses a dedicated worktree to isolate feature development before saving the structured plan to docs/plans.

The best way is creating a collaboration-ready implementation plan with a standard header, explicit execution handoff, and references to related skills for deployment and verification, saved as a date-stamped markdown file under docs/plans.

Breaking down implementation tasks into bite-sized steps ensures clear identification of files to touch, tests to write, and documentation to check, enabling structured execution handoff and parallel task management across teams.