Generate stepwise implementation plans with phases, tests-first criteria, and risk mitigation.
npx skills add https://github.com/samcdavid/dotfiles --skill my-plan
Please help me install this Agent Skill. Skill: my-plan Source: https://github.com/samcdavid/dotfiles/tree/main/claude/skills/my-plan Command: npx skills add https://github.com/samcdavid/dotfiles --skill my-plan
This skill provides a structured, interactive approach to create detailed, mechanically verifiable implementation plans that align teams and reduce rework.
Provide task details and context, and I will begin the planning workflow.
High-intent search queries and answers about installing and using this skill.
Implementation planning for complex initiatives requires structured context gathering, stakeholder alignment, and phased design. It targets complex product initiatives needing explicit success criteria, risk mitigation, and sections for architectural constraints and what is out of scope.
The best way to align stakeholders and reduce rework is through interactive context gathering and adversarial review. This iterative refinement process validates assumptions early, producing governance-ready artifacts that define explicit project boundaries like what is not being done.
Yes, you can use tests-first criteria to define software initiative phases. This method ensures each phase contains mechanically verifiable success checks, allowing teams to validate requirements and mitigate risks before progressing to the next development stage.
An adversarial review improves implementation plan feasibility by challenging assumptions and identifying potential risks during the design process. This iterative refinement reduces overlooked constraints, ensuring the final phased plan is robust and mechanically verifiable against success criteria.
Defining architectural constraints and out-of-scope items is essential for governance-ready implementation plans. Explicitly stating what is not being done sets clear boundaries for stakeholders, mitigating scope creep and ensuring the team focuses on defined phase requirements.
Risk mitigation and phased design are needed when planning complex product or software initiatives. If the project requires explicit success criteria, iterative stakeholder feedback, and structured context gathering, a phased plan reduces rework and ensures alignment.
coco-deTranslate stakeholder needs into clear product requirements and product briefs.
atomicinnovationExecute approved implementation plans and update progress checkboxes.
tanghuoReview documents for goal alignment, context verification, and risk identification.
drhazemibclcCoordinate phased brainstorming sessions to clarify user intent and capture design decisions.
