writing-plans

To break down a complex software feature into bite-sized implementation tasks, create a plan document specifying exact file paths, test steps, and verification criteria for reproducibility. Each task should take 2-5 minutes and follow a TDD-driven workflow.

A TDD-driven implementation plan structures tasks into a full cycle of writing tests, running them, implementing minimal code, validating, and committing to version control. This workflow ensures each bite-sized task is verified before moving forward.

You can use an implementation plan for documentation work, design tasks, and software features. The plan applies to any complex task requiring serial task execution, translating ambiguity into clear, actionable steps with exact files to touch.

The best way to structure an implementation plan for reproducibility is using a consistent header, per-task sections, and explicit verification steps. Ensure the plan includes exact file paths and test steps to guide implementation without ambiguity.

Your implementation plan fails to translate complex features into executable tasks when it lacks bite-sized task granularity. Without specifying exact files to touch, tests to write, and implementation steps, the plan remains ambiguous and hard to execute.