About pm-discovery
pm-discovery routes product discovery work to specialized frameworks for interviews, assumption testing, customer needs, prioritization, roadmaps, and briefs. It is intended for product teams that want a structured path from exploration to planning.
Key features
- 01Task-based framework routing
- 02Interview synthesis guidance
- 03Assumption testing route
- 04Needs discovery route
- 05Prioritization and roadmap routes
- 06Discovery synthesis template
Use cases
- 01Choosing a framework for a discovery task
- 02Organizing findings from research
- 03Prioritizing product features
- 04Moving discovery findings into planning
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/pm-discoveryin Claude Code to confirm it loaded.
Details
From the project READMEPM Discovery Orchestrator
Routes product discovery tasks to specialized frameworks.
Framework Routing
| Task | Skill | When to Use |
|---|---|---|
| Customer interviews | pm-customer-interviews | Conducting or synthesizing user interviews |
| Assumption testing | pm-assumption-mapping | Validating product hypotheses |
| Understanding needs | pm-jobs-to-be-done | Identifying why customers "hire" solutions |
| Feature prioritization | pm-prioritization | RICE/ICE scoring, opportunity mapping |
| Roadmap planning | pm-roadmap | Theme-based Now/Next/Later roadmaps |
| Feature briefs & decisions | pm-one-pager | Lightweight briefs, decision records |
When to Use Each
Interview synthesis needed? → pm-customer-interviews
Testing assumptions? → pm-assumption-mapping
Understanding motivation? → pm-jobs-to-be-done
Prioritizing features? → pm-prioritization
Planning roadmap? → pm-roadmap
Early exploration or recording decisions? → pm-one-pager
Full feature specification? → /majestic:prd
Discovery Synthesis
After using individual frameworks, synthesize findings:
## Discovery Summary: [Feature/Initiative]
### What We Learned
1. [Key insight with evidence]
2. [Key insight with evidence]
3. [Key insight with evidence]
### User Segments & Their Jobs
| Segment | Primary Job | Pain Intensity | Size |
|---------|-------------|----------------|------|
| [Segment A] | [JTBD] | [1-5] | [N users] |
### Prioritized Opportunities
| Rank | Opportunity | Evidence | RICE |
|------|-------------|----------|------|
| 1 | [Opp] | [Quote/data] | [Score] |
### Recommended Next Step
**Do:** [Specific action]
**Test:** [What to validate]
**Success looks like:** [Measurable outcome]
### What We Still Don't Know
- [ ] [Open question to investigate]
- [ ] [Assumption still untested]
Anti-Patterns
| Anti-Pattern | Why It Fails | Instead Do |
|---|---|---|
| Leading questions | Confirms bias | Ask open-ended |
| Hypothetical pricing | People lie | Ask current spending |
| Feature requests as truth | Solutions, not problems | Dig for need |
| Small sample decisions | Anecdotes ≠ patterns | 5+ signals minimum |
| Skip competitor research | Reinvent wheel | Research first |
Integration
- Before: Use
problem-researchfor market pain points - After: Use
/majestic:prdfor requirements documentation - After: Use
/majestic:planfor implementation planning
Comments
Markdown supported