writing-plans

To plan multi-step tasks before coding, break specifications into small, verifiable steps with precise file mappings and testing strategies. This enforces DRY, YAGNI, and TDD principles while establishing clear task boundaries and documenting required changes.

The best way to break down features for TDD is creating a granular, task-based implementation plan that guides you to write failing tests first, then implement and iterate. This aligns execution with test-driven development workflows.

To ensure tasks are independent and testable in a worktree, establish a plan-first workflow that defines clear task boundaries before touching any code. This isolates multi-step features spanning multiple subsystems.

You need a granular implementation plan for multi-step features that span multiple files or subsystems where you have limited codebase context. It requires documenting every file change, testing step, and evidence of progress upfront.

Yes, plan-first task splitting works without deep codebase knowledge because it assumes developers have limited context and emphasizes documenting every required file change and testing step before writing any code.

A limitation of writing detailed plans before touching code is the overhead required for multi-step tasks. It enforces strict DRY, YAGNI, and TDD principles with specific checkpoints, which may not suit rapid prototyping or single-file changes.