writing-plans

To create a detailed implementation plan, you need to outline file modifications, code snippets, testing steps, and commit messages. This skill generates bite-sized, step-by-step plans ensuring developers have all necessary context without prior codebase knowledge.

The best way to document implementation steps is to generate bite-sized plans with exact file modifications, code snippets, and testing procedures. This approach defines a clear handoff for plan execution through parallel sessions or subagent-driven development.

Writing an implementation plan with zero prior context requires detailing every file to touch, exact code snippets, and testing procedures. The plan assumes no prior knowledge of the codebase, ensuring clarity by providing comprehensive instructions for the implementer.

Yes, you can include specific commit messages and testing steps in your plan. The generated implementation plans outline every file to touch, exact code snippets, testing procedures, and frequent commit messages to ensure structured development.

Yes, this implementation planning approach works with TDD and DRY principles. The generated plans explicitly adhere to Test-Driven Development, Don't Repeat Yourself, and YAGNI principles to ensure structured and maintainable software development.

You should not use a detailed implementation plan for trivial software development tasks that do not require multi-step instructions. The plans are designed for complex multi-step tasks requiring file modifications, code snippets, and defined testing steps.