writing-plans

To create a step-by-step implementation plan, provide a clear feature name and context. The plan breaks down tasks into actionable steps including specific file modifications, code examples, testing procedures, and commit strategies.

The best way to break down a multi-step task is to generate bite-sized, actionable steps that outline every file to modify, exact tests to write, and commit messages to use, ensuring a smooth development process.

Yes, you can generate a task breakdown that provides specific file paths, code snippets, and contextual testing instructions. This gives engineers with zero codebase context all necessary information for task completion.

Implementation plan generation works with TDD and DRY principles by adhering to them during plan creation. It outlines exact tests to write and code examples to use, ensuring the development process follows these methodologies.

You need to provide a clear feature name and relevant project context for plan generation. This allows the system to generate detailed, step-by-step instructions with specific file modifications and testing procedures.

You should generate an implementation plan before starting a new feature to ensure you have clear, actionable, and comprehensive instructions. This addresses the challenge of providing engineers with all necessary context and instructions for software development tasks.