pm-discovery

产品经理的产品发现框架 - 客户访谈、假设映射、JTBD、RICE 优先级排序和机会解决方案树。将研究转化为产品决策。

📖 中文导读:产品经理的产品发现框架 - 客户访谈、假设映射、JTBD、RICE 优先级排序和机会解决方案树。将研究转化为产品决策。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: pm-discovery description: Product discovery orchestrator - routes to specialized frameworks for interviews, assumptions, JTBD, and prioritization. triggers: - pm discovery - product discovery

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