writing-plans

To create an implementation plan for a multi-step coding task, define bite-sized steps covering file touch points, tests, documentation, and commit notes. Structure the plan with a clear header and save it to docs/plans/YYYY-MM-DD-<feature-name>.md for traceability.

Test-driven development planning for evolving specifications works by breaking down requirements into bite-sized task steps that define tests to write alongside file modifications. This approach emphasizes DRY and YAGNI principles to keep the evolving implementation efficient and testable.

The best way to structure planning documentation before coding is to include a dedicated plan header, task-level steps, specific file paths, test steps, and version-control commands. This ensures the plan is implementation-ready and completely traceable.

Yes, you need a dedicated worktree setup to plan multi-step software engineering tasks effectively. Using a worktree isolates the upcoming implementation changes, keeping the plan organized and separate from your main development branch.

Yes, you can use this planning workflow if your requirements are still changing. It explicitly covers scenarios where specifications are evolving, guiding you through incremental file touch points, tests, and commit notes as the design adapts.

You should write a complete plan before touching code to ensure your multi-step tasks are fully implementation-ready. It forces you to map out file paths, test steps, and version-control commands upfront, preventing scope creep and maintaining traceability.