writing-plans

To generate an implementation plan, use this Skill to break down coding tasks into bite-sized steps. It provides exact file paths, code snippets, testing commands, and commit messages to ensure zero context is needed.

The best way to create a TDD-focused task breakdown is to use a planning tool that enforces TDD, DRY, and YAGNI principles. This Skill outlines every required test and code change before implementation begins.

Yes, the generated implementation plan includes exact file paths, code snippets, testing commands, and commit messages. This ensures engineers have all necessary context without prior codebase knowledge.

Yes, you can use this approach for engineers with no prior domain knowledge. The generated plans assume zero context, explicitly detailing every required test, code change, and commit for the implementation.

Implementation plans enforce DRY and YAGNI principles by structuring the task breakdown to explicitly avoid repetition and unnecessary features. The generated steps ensure engineers only build what is required.