Generate detailed implementation plans with TDD, DRY, and YAGNI principles.
npx skills add https://github.com/KanuToCL/SonoTag --skill writing-plans-kanutocl
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/KanuToCL/SonoTag/tree/main/.claude/skills/writing-plans Command: npx skills add https://github.com/KanuToCL/SonoTag --skill writing-plans-kanutocl
This Skill helps engineers by creating detailed, step-by-step implementation plans for multi-step tasks, ensuring clarity and reducing the need for extensive prior context.
Use the writing-plans skill to generate an implementation plan for adding a new user authentication module.
High-intent search queries and answers about installing and using this skill.
Implementation planning for multi-step tasks breaks features down into bite-sized, executable steps. This approach ensures clarity and reduces the need for engineers to have extensive prior context about the codebase or problem domain.
Task breakdown for limited context involves creating granular, executable steps that include exact code snippets and testing commands. This ensures smooth development by outlining every file to touch without assuming prior codebase knowledge.
Implementation planning for TDD includes specific testing commands and code snippets alongside implementation steps. This ensures test-driven development practices are embedded directly within the generated task breakdown for the software feature.
Yes, implementation planning works for a new user authentication module. It generates a comprehensive plan outlining every file to touch, exact code snippets for tests and implementation, and the commands to run for smooth execution.
The best way to document file paths and commit messages is to generate an implementation plan that explicitly includes them. This ensures every granular step has exact code snippets, testing commands, and commit messages for smooth execution.
You should avoid automated implementation planning for simple, single-step tasks or when the feature requires highly specialized domain logic outside standard TDD principles. It is designed specifically for complex, multi-step software development tasks requiring granular breakdowns.
nicograefGenerate phased implementation plans from product requirements into Markdown documentation.
musical-basicsGenerate implementation plans with file paths, code snippets, and TDD steps.
windyskyGenerate documentation patterns from code for Sphinx, MkDocs, TypeDoc, and Nextra.
juvenalExecute pre-planned feature implementation task lists in dependency-aware order with TDD.
