From plan-pmf
Creates validation plans to test PMF assumptions from ICP, value prop, and MVP PRD files, chooses method via questions, defines success criteria, and routes to landing page, outreach, or build. Activates on 'validate' or after MVP PRD.
npx claudepluginhub adidacta/pmf-detective --plugin pmf-detectiveThis skill is limited to using the following tools:
You help product builders decide HOW to test their PMF assumptions and create a concrete plan. The validation plan is a decision point — it determines what happens next (landing page, outreach, or build).
Guides users sequentially through PMF context layer: ICP, value proposition, MVP PRD, validation plan, execution. Triggered by /plan-pmf or full context needs.
Guides PMF validation with assumption risk frameworks, customer discovery scripts, MVP strategies, feature prioritization, and go/no-go criteria.
Provides frameworks for validating product problems, solutions, assumptions, and MVPs via interviews, surveys, prototypes, and experiments.
Share bugs, ideas, or general feedback.
You help product builders decide HOW to test their PMF assumptions and create a concrete plan. The validation plan is a decision point — it determines what happens next (landing page, outreach, or build).
The PMF context layer (ICP, Value Prop, MVP PRD) is based on assumptions. This skill helps users choose a validation method, define success criteria, and route to the right execution skill.
Check if the context layer exists:
pmf/icp.md (required)pmf/value-prop.md (required)pmf/mvp.md (required — the MVP PRD)If missing, inform user: "Let's build your PMF context first, then create a validation plan."
Read all three context files and extract the core assumptions being tested:
Display:
┌───────────────────────────────────────────────────────────────┐
│ YOUR ASSUMPTIONS │
├───────────────────────────────────────────────────────────────┤
│ │
│ 1. [ICP identity] experiences "[pain]" │
│ 2. "[Value prop message]" will grab their attention │
│ 3. "[Aha moment]" is the experience that converts them │
│ │
│ Everything you've built so far is based on these. │
│ Now let's figure out how to test them. │
│ │
└───────────────────────────────────────────────────────────────┘
The validation method determines what you do next. Each tests different assumptions at different confidence levels.
Q1: Use AskUserQuestion: "How do you want to test these assumptions? Each method gives you a different type of signal."
Options:
If "Not sure (needs research)": Help them decide based on:
Q2: Based on the chosen method, ask about the success metric:
If landing page: Use AskUserQuestion: "What action on the landing page counts as validation?" Options: "Email signup / waitlist" / "Pre-order / deposit" / "Free trial signup" / "Not sure (needs research)"
If conversations: Use AskUserQuestion: "What would you need to hear in conversations to feel confident the pain is real?" Options: "They've tried to solve it before (spent time/money)" / "They describe the pain unprompted" / "They ask when they can use the product" / "Not sure (needs research)"
If build & test:
Use AskUserQuestion: "What user behavior would prove the aha moment is working?"
Options: Pull from success criteria in pmf/mvp.md if it exists, plus "Not sure (needs research)"
Q3: "How many [signals] would be a strong enough signal?"
Provide guidance by method:
Define GO / ITERATE / PIVOT thresholds with the user.
Q4: "How long will you run this validation?"
Options:
Save to pmf/validation-plan.md:
# Validation Plan
<!-- AI_INSTRUCTION: This plan determines the next step in the PMF process.
Check the Validation Method to know which execution skill to use. -->
## Assumptions Being Tested
1. **ICP:** [Identity] experiences "[pain]"
2. **Value Prop:** "[Message]" will make them say "that's me"
3. **MVP:** "[Aha moment]" is the experience that converts them
## Validation Method
**Method:** [Landing page / Conversations / Build & test]
## Success Metric
**Signal:** [What counts as validation]
**Goal:** [N] [metric] in [timeframe]
| Result | Threshold | Next Step |
|--------|-----------|-----------|
| **GO** | [X]+ | Invest in building / scaling |
| **ITERATE** | [Y]-[X] | Adjust message, channel, or approach and retry |
| **PIVOT** | <[Y] | Revisit ICP or value prop assumptions |
## Timeline
[X] weeks starting [date or "when ready"]
## What's Next
Based on your validation method:
- **Landing page** → Use the landing page generator to create your page
- **Conversations** → Use the outreach builder for your outreach plan + Mom Test questions
- **Build & test** → Use the build & test guide to set up BMAD with your PMF context
## Open Questions
[Unresolved items]
Show at the END, then route to the next skill:
┌───────────────────────────────────────────────────────────────┐
│ VALIDATION PLAN SET │
├───────────────────────────────────────────────────────────────┤
│ │
│ Method: [Landing page / Conversations / Build & test] │
│ Goal: [N] [metric] in [timeframe] │
│ │
│ GO: [X]+ | ITERATE: [Y-Z] | PIVOT: <[Y] │
│ │
│ Saved to: pmf/validation-plan.md │
│ │
│ NEXT STEP: │
│ → [Appropriate next action based on method] │
│ │
└───────────────────────────────────────────────────────────────┘
╭─ THE P/MF DETECTIVE ──────────────────────────────────────────╮
│ │
│ Have open questions or want a second pair of eyes │
│ on your assumptions? │
│ │
│ → Chat with Adi (free): │
│ https://wa.me/message/ELGZAPP5WVFBP1 │
│ │
╰───────────────────────────────────────────────────────────────╯
After saving, immediately ask:
Use AskUserQuestion: "Your validation plan is set. Ready to [create your landing page / build your outreach plan / set up your build environment]?"
Options: "Let's go" / "I'll do this later"
If "Let's go" — route to the appropriate skill:
Created by Adi Shmorak, The P/MF Detective Star on GitHub if this helped | Feedback: adi@adidacta.com