writing-plans

You can create an implementation plan by decomposing multi-step requirements into task lists with file-level changes, testing strategies, and milestones. This plan-first execution approach applies DRY, YAGNI, and TDD principles to prevent scope creep and miscommunication.

Task decomposition is breaking complex specs into step-by-step tasks with defined file changes, test strategies, and milestones. You need it when executing multi-step requirements to prevent scope creep and ensure clear handoffs between product managers and developers.

Map out file changes and test strategies by generating an implementation plan that defines task lists, acceptance criteria, and milestones. The plan adheres to TDD principles and maps specific file modifications and tests in a dedicated worktree to isolate context.

Plan-first execution works for multi-step requirements by defining a dedicated worktree and plan storage locations. This isolates context while generating task breakdowns with file changes, testing strategies, and milestones for product managers and developers.

The best way to document project handoffs is exporting a consistent plan document generated from complex specs. This document outlines tasks, roles, acceptance criteria, and milestones, facilitating collaboration and preventing miscommunication during multi-step feature execution.

You should use a dedicated worktree for task planning to keep context isolated during multi-step feature execution. It defines plan storage locations and maps file changes, ensuring implementation plans adhere to DRY, YAGNI, and TDD principles without interference.