writing-plans

To generate a detailed implementation plan, break down complex software development tasks into bite-sized actions including writing failing tests, implementing minimal code, running tests, and committing changes. This ensures clarity and consistency by providing exact file paths and commands for engineers with zero codebase context.

The best way to break down multi-step coding tasks is to generate step-by-step instructions assuming zero prior knowledge. Provide exact file paths, commands, and specific actions like writing failing tests and implementing minimal code to ensure a smooth development process.

To create a TDD implementation plan, outline every file to modify and every test to write. Break the workflow into small, manageable actions: write failing tests, implement minimal code, run tests, and commit changes, ensuring all necessary commands and paths are explicitly detailed.

Yes, automated task breakdown works for adding new authentication flows without prior codebase knowledge. It generates context-aware instructions that outline every file to modify, every test to write, and every command to run, assuming zero prior context for the engineer.

Yes, this implementation planning approach works for adding user profile editing functionality. It generates a comprehensive, step-by-step plan that outlines exact file paths, test cases, and commands, ensuring a smooth development process even for complex multi-step tasks.

You need a detailed coding plan when tackling complex multi-step tasks that require clear, actionable implementation steps. It is crucial for ensuring clarity and consistency, especially when the engineer executing the tasks has limited context of the codebase.