writing-plans

An implementation plan structures multi-step coding tasks by defining exact file touchpoints, testing steps, documentation references, and explicit handoffs before coding starts. It breaks complex features into bite-sized tasks for engineers lacking context.

Task breakdown in software engineering decomposes complex features into bite-sized actionable steps with required files, tests, docs, and commits. It enforces DRY, YAGNI, and TDD best practices to standardize execution and enable rapid onboarding.

Write a TDD plan document using a standardized structure featuring a Plan Document Header and Task Structure, saved to docs/plans/YYYY-MM-DD-<feature-name>.md. This enforces TDD best practices while providing explicit handoffs for engineers.

Yes, you can draft implementation plans in a dedicated worktree. Announce your planning approach upfront and use the isolated worktree environment to generate comprehensive task breakdowns with exact file touchpoints and testing steps before coding begins.

Yes, implementation planning targets scenarios where engineers lack context by providing bite-sized tasks with explicit handoffs and standardized plan structures. This enables rapid onboarding and consistent execution across teams working on complex multi-step tasks.

Standardized plan documents require strict adherence to the Plan Document Header and Task Structure format. For simple or single-step tasks, the overhead of generating exact file touchpoints, testing steps, and explicit handoffs may outweigh the benefits of formal planning.