writing-plans

To generate an implementation plan, provide a feature goal and constraints to produce a comprehensive, task-by-task plan with exact file paths, code templates, testing commands, and verification steps. This breaks down vague requirements into bite-sized, actionable development tasks.

Creating bite-sized tasks for multi-phase features involves breaking down the specification into explicit file-level guidance, complete example code, and documentation references. This approach ensures every task adheres to TDD and DRY principles while providing precise instructions for developers.

Yes, you can use implementation plans for cross-team handoffs. They deliver a repeatable, task-by-task plan structure that facilitates team transitions and aligns stakeholders by providing concrete task instructions, exact file paths, and clear verification steps.

Yes, this implementation planning approach fully supports TDD and DRY principles. It outputs bite-sized tasks that include complete code examples, specific testing commands, and verification steps, ensuring the generated development plan adheres to established software engineering standards.

To generate an implementation plan, you need to provide a high-level feature goal and any project constraints. The system then outputs a comprehensive plan containing precise file paths, code templates, testing commands, and documentation references for the development tasks.

Creating technical implementations from vague specifications is time-consuming and error-prone. A task-by-task implementation plan accelerates delivery by specifying exact file paths, code templates, and verification steps, reducing errors and ensuring alignment across multi-phase software features.