writing-plans

To generate a step-by-step implementation plan, you define the feature and the planner breaks it down into 2-5 minute actionable tasks. It provides exact file paths, code snippets, testing instructions, and commit messages for each step.

Task breakdown divides complex development into 2-5 minute actions, specifying exact tests to write and run. It supports TDD by sequencing test creation before code generation, ensuring frequent commits and structured testing throughout the workflow.

No, you do not need prior codebase knowledge to create a detailed development plan. The planning process assumes minimal developer context and automatically provides necessary guidance, including exact file paths and code snippets for each task.

Yes, an automated task breakdown provides exact file paths, code snippets, and commit messages for each step. It structures the development process into actionable tasks that facilitate frequent commits and clear documentation.

The best way to plan multi-step coding tasks is to use a structured planning approach that generates bite-sized actions. This method outlines every file to modify, test to write, and command to run, ensuring a smooth and efficient development process.

You should not use automated implementation plans for code generation when facing single-step tasks or highly exploratory programming that lacks defined testing requirements. The tool is designed for multi-step tasks requiring structured breakdown and frequent commits.