my-plan

Generate stepwise implementation plans with phases, tests-first criteria, and risk mitigation.

4|1|Updated May 31, 2015

Search Tags:#planning #testing #requirements #risk-management #phases #stakeholders #plan-writing

Ready to run

npx skills add https://github.com/samcdavid/dotfiles --skill my-plan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured, interactive approach to create detailed, mechanically verifiable implementation plans that align teams and reduce rework.

Core Features & Use Cases

Interactive context gathering and alignment with stakeholders.
Research-driven planning with clear phase definitions and risk mitigation.
Tests-first planning: each phase defines explicit success criteria that are runnable checks.
Adversarial review and iterative plan refinement to reduce assumptions and improve feasibility.
Generates governance-ready artifacts, including What We're NOT Doing.

Quick Start

Provide task details and context, and I will begin the planning workflow.

Frequently Asked Questions about my-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a mechanically verifiable implementation plan for a software project?▼

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.

What is the best way to align stakeholders and reduce rework during product planning?▼

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.

Can I use tests-first criteria to define phases for complex software initiatives?▼

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.

How does an adversarial review process improve implementation plan feasibility?▼

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.

Do I need to define architectural constraints and out-of-scope items in a project plan?▼

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.

When do I need risk mitigation and phased design for product management initiatives?▼

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.