the-controller-writing-plans

You generate an implementation plan by defining specific file modifications, test writing, minimal code implementation, and commit steps before touching any code. This approach assumes zero prior codebase context, ensuring all necessary information is documented.

TDD-focused implementation planning is outlining explicit steps for writing failing tests and verifying passes before coding. You need it before starting any new feature or task to ensure clarity and reduce the need for extensive prior context.

You write a step-by-step implementation plan by detailing bite-sized tasks: file modifications, writing tests, implementing minimal code, and committing. This structured approach guides developers through each stage of implementation from tests to commits.

Yes, you can create a development plan without prior context by requiring all necessary information to be documented within the plan itself. This ensures developers have zero context about the codebase but can still follow the detailed steps.

Yes, this implementation planning approach works for adding a user authentication module by generating a detailed plan that guides you through each stage. It outlines file modifications, tests, minimal implementation, and commits for the new module.

A limitation is that generating detailed implementation plans requires all necessary codebase information to be explicitly documented upfront. It assumes zero prior context, meaning you must provide comprehensive details for the plan to be effective.