pm-discovery

Product discovery frameworks for PMs - customer interviews, assumption mapping, JTBD, RICE prioritization, and opportunity solution trees. Transforms research into product decisions.

⭐13stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026⬇️4downloads

When & Why to Use This Skill

The PM Discovery Orchestrator is a comprehensive Claude skill designed to streamline the product discovery process for Product Managers. It integrates industry-standard frameworks—including JTBD, RICE prioritization, and assumption mapping—to transform raw customer research into data-driven product decisions and validated roadmaps, helping teams avoid common pitfalls like confirmation bias and hypothetical questioning.

Use Cases

  • Synthesizing customer interviews: Automatically extracting key insights and evidence from user conversations to identify recurring pain points.
  • Assumption validation: Mapping and testing critical product hypotheses to reduce development risk before committing resources.
  • Jobs-to-be-Done (JTBD) analysis: Identifying the underlying motivations and 'hiring' criteria of different user segments to improve product-market fit.
  • Data-driven prioritization: Using RICE/ICE scoring and opportunity solution trees to objectively rank features and initiatives based on impact and effort.
  • Strategic handoffs: Generating structured discovery summaries that bridge the gap between initial research and PRD/implementation planning.
namepm-discovery
descriptionProduct discovery orchestrator - routes to specialized frameworks for interviews, assumptions, JTBD, and prioritization.

PM 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

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

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-research for market pain points
  • After: Use /majestic:prd for requirements documentation
  • After: Use /majestic:plan for implementation planning