Writing Plans

To generate an implementation plan, you provide the feature design and the tool outputs bite-sized tasks including file modifications, code snippets, testing procedures, and commit messages for the entire development process.

Breaking down complex software development tasks involves creating bite-sized, actionable steps that take two to five minutes each, ensuring clarity and providing explicit instructions and expected outcomes for every step.

Yes, you can generate context-free engineering plans that provide all necessary information, including file paths, code snippets, and testing commands, enabling engineers with zero prior knowledge of the codebase to execute tasks.

Task breakdown improves development efficiency by transforming complex features into small, actionable steps with explicit instructions, testing procedures, and commit messages, which reduces ambiguity and ensures clear expected outcomes.

An implementation plan should include bite-sized tasks, specific file modifications, code implementation details, testing procedures, and commit messages to ensure complete clarity for engineers joining the development team.

You need to generate detailed engineering plans when a new feature is designed and you must detail every test, implementation step, and commit required to ensure a clear and efficient development process.