Generate TDD implementation plans with exact file paths and code examples.
npx skills add https://github.com/mikeyobrien/ghclip --skill writing-plans-mikeyobrien
Please help me install this Agent Skill. Skill: writing-plans Source: https://github.com/mikeyobrien/ghclip/tree/main/.claude/skills/writing-plans Command: npx skills add https://github.com/mikeyobrien/ghclip --skill writing-plans-mikeyobrien
This Skill automates the creation of highly detailed, bite-sized implementation plans for engineers, minimizing ambiguity and ensuring adherence to TDD principles. It saves significant time in planning, reduces implementation errors, and ensures consistent quality across development tasks.
docs/plans/YYYY-MM-DD-<feature-name>.md) with mandatory architectural and technical headers.Use the writing-plans skill to create an implementation plan for adding a new user authentication feature.
High-intent search queries and answers about installing and using this skill.
Implementation plans break down features into 2-5 minute TDD cycles: write failing test, verify failure, implement, verify passing, commit. This skill generates bite-sized tasks with exact file paths, complete code examples, and verification steps saved to docs/plans, reducing ambiguity and implementation errors.
Effective implementation plans contain exact file locations, runnable code samples, specific test commands with expected outcomes, and clearly defined commit points. This ensures any engineer, regardless of codebase familiarity, can follow the plan precisely and pass review without rework.
Yes. Implementation plans work for projects requiring structured task breakdown following software architecture principles. They apply TDD rigor to architecture decisions, delivering detailed deliverables with mandatory technical and architectural headers stored in standardized documentation paths.
Task breakdown into 2-5 minute increments with exact deliverables and verification steps minimizes planning ambiguity and reduces implementation errors. Each task specifies file paths, code examples, and commit points, enabling consistent quality and faster engineer execution.
Implementation plans are saved as markdown files in docs/plans/YYYY-MM-DD-<feature-name>.md with mandatory architectural and technical headers. This standardized structure enables consistent project documentation and easy retrieval across teams.
Generate plans for features requiring TDD adherence, multiple team members, or minimal context sharing. Automated planning eliminates manual ambiguity, ensures consistent TDD cycles, and saves significant time compared to writing detailed step-by-step guides by hand.
jshsakuraDefine risk-based test scope and acceptance criteria for software releases.
bacocoImplement approved OpenSpec proposals by executing tasks and recording test evidence.
SkogAIGenerate detailed implementation plans with file paths, code samples, and tests.
g-zenrDecompose feature scopes into user stories, tasks, and risk assessments.