writing-plans

To generate a detailed implementation plan, define the software development task and require the skill to output file modifications, test creation steps, and execution commands for engineers with zero prior context.

Task breakdown in TDD implementation planning is the process of splitting software features into bite-sized steps that specify file modifications, test writing, and execution commands to ensure frequent commits and clarity.

Writing implementation plans for engineers with no prior context involves structuring the document with a specific header and task breakdown, explicitly detailing every file modification, test, and execution command required.

Yes, the implementation planning approach requires adherence to a specific plan document header and task structure to maintain clarity and consistency across all generated software development guides.

The best way to plan file modifications and test writing for a new feature is to automate the creation of a step-by-step guide that emphasizes TDD, execution commands, and frequent commits for zero-context engineers.

Yes, you can use this for task breakdown and documentation of complex software tasks, as it reduces ambiguity by automating the creation of comprehensive, bite-sized implementation plans with specific execution steps.