nobody-writes-plans

To generate a step-by-step implementation plan, outline the specific feature requirements and let the tool map out file modifications, test creation, and verification commands. This produces a detailed, bite-sized workflow covering exact code and expected outputs for structured development.

The best way to plan a multi-step software development task with TDD is to document every file modification, test script, and minimal code implementation beforehand. This approach ensures adherence to TDD, DRY, and YAGNI principles by defining exact verification steps and expected outputs.

Yes, you can use this planning workflow for any software development environment because it generates context-aware instructions that assume zero prior context. It systematically documents the exact commands and code needed, making it adaptable across different platforms and tech stacks.

Detailed implementation planning complements existing documentation by providing bite-sized, actionable steps for new features rather than broad architectural overviews. It focuses on exact file modifications, test writing, and specific verification commands to ensure structured development workflows.

You should write an implementation plan before coding to ensure all necessary details, file modifications, and test requirements are considered upfront. This prevents scope creep and reduces errors by enforcing TDD, DRY, and YAGNI principles through clear, actionable verification steps.

The limitation of generating implementation plans for complex tasks is that the output is only as accurate as the provided feature description. While it maps out file modifications and test commands, unexpected architectural dependencies may still require manual adjustments during the actual coding phase.