writing-plans

To create an implementation plan, this Skill generates a detailed, step-by-step task breakdown that includes specific file paths, code snippets for tests and implementation, exact commands, and commit messages for your software development task.

The best way to break down a coding feature is to generate bite-sized, actionable steps that outline exact file modifications, testing instructions, and commit messages, ensuring clarity for developers with zero codebase context.

Yes, you can generate test-driven development plans that provide specific file paths, code snippets for tests and implementation, exact commands, and commit messages, emphasizing TDD and frequent commits throughout the process.

Yes, this implementation planning approach works for multi-step tasks without external dependencies, generating contextual information and actionable steps natively to minimize ambiguity for the developer.

You need an implementation plan with exact commit messages and test snippets to ensure engineers have all necessary context and steps, minimizing ambiguity and providing clear, actionable instructions for development tasks.

A limitation of using a generated task breakdown is that it functions as an intermediate-level planning tool, meaning the quality of the detailed steps, code snippets, and commit messages depends entirely on the initial task context provided.