How do I install the Pm Discovery skill?

Run npx skillmds add majiayu000/pm-discovery in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pm Discovery safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pm Discovery?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pm Discovery free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pm Discovery?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pm Discovery by majiayu000 — Agent Skill

Name: Pm Discovery
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

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

---name: pm-discoverydescription: Product 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: ```markdown ## 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

Frequently asked questions