writing-plans

Implementation plans are generated by breaking down feature specifications into small, TDD-oriented tasks with exact file paths, testing commands, and expected outcomes. This process creates a review-ready plan covering architecture, implementation order, and commit strategy before coding begins.

Breaking down multi-step software work involves splitting large feature scopes into independently deliverable subprojects and assigning single responsibilities to exact files. This task breakdown method ensures coordinated subsystem changes are organized into small, concrete steps for direct execution.

A dedicated worktree is required for planning coordinated subsystem changes spanning multiple files, tests, and documentation. Planning within a worktree ensures isolated scope checks and review-ready handoff instructions are established before any implementation starts.

Test-driven tasking decomposes work into small, concrete steps that include specific tests, commands, and expected outcomes. This ensures the resulting implementation plan is directly executable and aligns with TDD practices before the actual coding phase begins.

Large feature requests are split into independently deliverable subprojects when the specification spans multiple subsystems. This scope splitting ensures complex features are organized into manageable, reviewable plans that cover architecture and implementation order.

File-first planning is not suitable for simple features that do not span multiple files, tests, or documentation. It requires exact file paths and multi-step coordinated subsystem changes to effectively utilize its detailed task breakdown and TDD-oriented structure.