Skip to main content
skill CX Codex

product-management — Claude Code skill: what it does, how to install

product-management equips your agent with product strategy frameworks: RICE scoring, roadmap horizons, OKR setups, and PMF validation surveys.

MIT 153 installs ★ 114 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add travisjneuman/.claude --skill product-management -a claude-code
Open on GitHub

What product-management does

This skill supplies common product frameworks right inside your terminal sessions. It outlines feature scoring using RICE and ICE formulas, the MoSCoW classification, and the Kano model. For customer discovery, it includes Sean Ellis's 40% benchmark for product-market fit alongside the four growth stages.

Roadmap planning splits into four clear horizons, ranging from short two-week sprints to multi-year vision roadmaps. It also defines OKR targets and AARRR Pirate Metrics with baseline ratios for DAU/MAU and activation rates. Deep-dive guides depend on Markdown documents in the references/ folder; ensure those files are present in the skill directory.

What it helps with

  • score product backlog features with RICE or ICE formulas
  • draft team OKRs tied to churn and contract values
  • prepare Sean Ellis survey questions to measure product-market fit
  • structure experiment hypotheses for upcoming A/B tests

Example prompts for the agent

  • Calculate RICE scores for these candidate features using quarterly reach and effort estimates
  • Draft an Amazon-style press release for our new enterprise search feature
  • Define a JTBD statement analyzing current push and pull dynamics for switching

How to install product-management

1Skills CLI (Vercel)

npx skills add travisjneuman/.claude --skill product-management -a claude-code

2Manually: put the files in place

~/.claude/skills/product-management/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/product-management/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about product-management

How do I install product-management in Claude Code?

Run npx skills add travisjneuman/.claude --skill product-management -a claude-code in your terminal.

What prioritization models does this skill provide?

It provides calculation formulas for RICE and ICE, alongside MoSCoW categorization and the Kano model.

What external files does the skill reference?

It references customer-research-methods.md and analytics-and-experimentation.md inside the references/ directory for detailed interview protocols.

Source text

SKILL.md · MIT
---
name: product-management
description: Product management expertise for product strategy, roadmap planning, feature prioritization (RICE, ICE, MoSCoW), customer research, A/B testing, product analytics, and product-market fit. Use when building product roadmaps, prioritizing features, or defining product strategy.
---

# Product Management Expert

Comprehensive product frameworks for strategy, roadmapping, prioritization, and product-market fit.

## Product Strategy

### Product Vision Framework

```
VISION COMPONENTS:

TARGET CUSTOMER:
- Who are we building for?
- What segments? What personas?

CUSTOMER NEED:
- What problem are we solving?
- What job to be done?

KEY BENEFIT:
- Primary value proposition
- Why customers will choose us

DIFFERENTIATOR:
- What makes us unique?
- Competitive advantage

AMAZON PRESS RELEASE FORMAT:
- Headline
- Summary (who, what, when, where, why)
- Problem statement
- Solution description
- Customer quote
- How to get started
```

### Product-Market Fit

```
PMF INDICATORS:

QUANTITATIVE:
- 40%+ would be "very disappointed" without product (Sean Ellis)
- Strong organic growth/referrals
- Low churn, high retention
- Improving unit economics

QUALITATIVE:
- Customers actively advocating
- Word of mouth driving acquisition
- Pull from market (not push)
- Customers expanding usage

PMF SURVEY:
"How would you feel if you could no longer use [product]?"
- Very disappointed → Target 40%+
- Somewhat disappointed
- Not disappointed

PMF STAGES:
1. Problem-Solution Fit: Validated problem worth solving
2. Product-Market Fit: Solution resonates with market
3. Business Model Fit: Sustainable economics
4. Scale: Growth mechanics work
```

### Jobs to Be Done (JTBD)

```
JOB STATEMENT:
When [situation], I want to [motivation], so I can [expected outcome].

FORCES OF PROGRESS:
Push: Current pain/frustration
Pull: Attraction to new solution
Anxiety: Concerns about switching
Habit: Comfort with status quo
```

See [Customer Research Methods](./references/customer-research-methods.md) for detailed JTBD methodology and interview techniques.

## Roadmap Planning

### Roadmap Types

| Type          | Timeframe  | Audience            | Detail Level |
| ------------- | ---------- | ------------------- | ------------ |
| **Vision**    | 2-5 years  | Board, executives   | Themes       |
| **Strategic** | 1-2 years  | Leadership          | Initiatives  |
| **Release**   | 3-6 months | Teams, stakeholders | Features     |
| **Sprint**    | 2-4 weeks  | Dev team            | User stories |

### OKR Framework for Product

```
PRODUCT OKR STRUCTURE:

OBJECTIVE: [Qualitative goal]

KEY RESULT 1: [Metric] from [X] to [Y]
KEY RESULT 2: [Metric] from [X] to [Y]
KEY RESULT 3: [Metric] from [X] to [Y]

EXAMPLE:
O: Become the preferred solution for enterprise customers
KR1: Increase enterprise NPS from 40 to 60
KR2: Reduce enterprise churn from 8% to 4%
KR3: Increase enterprise ACV from $50K to $75K
```

## Feature Prioritization

### RICE Framework

```
RICE SCORE = (Reach x Impact x Confidence) / Effort

REACH: How many customers affected per quarter
- Count: Number of users, customers, transactions

IMPACT: Effect on individual customer
- 3 = Massive
- 2 = High
- 1 = Medium
- 0.5 = Low
- 0.25 = Minimal

CONFIDENCE: How sure are we
- 100% = High confidence
- 80% = Medium
- 50% = Low

EFFORT: Person-months of work
- Engineering time
- Design time
- PM time

EXAMPLE:
| Feature | Reach | Impact | Conf | Effort | RICE |
|---------|-------|--------|------|--------|------|
| A | 5000 | 2 | 80% | 3 | 2667 |
| B | 1000 | 3 | 100% | 1 | 3000 |
| C | 10000 | 1 | 50% | 5 | 1000 |
```

### ICE Framework

```
ICE SCORE = Impact x Confidence x Ease

IMPACT (1-10):
How much will this move our key metric?

CONFIDENCE (1-10):
How sure are we about impact estimate?

EASE (1-10):
How easy to implement?

Note: Simpler than RICE, good for quick decisions
```

### MoSCoW Method

| Category        | Definition                  | Guidance              |
| --------------- | --------------------------- | --------------------- |
| **Must Have**   | Non-negotiable for release  | Core functionality    |
| **Should Have** | Important but not critical  | High value, can defer |
| **Could Have**  | Nice to have                | If time permits       |
| **Won't Have**  | Out of scope (this release) | Future consideration  |

### Kano Model

```
CATEGORIES:

BASIC (Must-be):
- Expected features
- Absence causes dissatisfaction
- Example: Login functionality

PERFORMANCE (Linear):
- More is better
- Satisfaction proportional to fulfillment
- Example: Speed, capacity

DELIGHTERS (Excitement):
- Unexpected features
- Absence doesn't cause dissatisfaction
- Presence greatly increases satisfaction
- Example: Innovative features
```

## Customer Research

### Research Methods

| Method              | When to Use              | Sample Size | Time      |
| ------------------- | ------------------------ | ----------- | --------- |
| **User Interviews** | Deep understanding       | 5-15        | 2-4 weeks |
| **Surveys**         | Quantify findings        | 100-1000+   | 1-2 weeks |
| **Usability Tests** | Validate designs         | 5-8         | 1-2 weeks |
| **A/B Tests**       | Compare options          | 1000+       | 2-4 weeks |
| **Analytics**       | Understand behavior      | N/A         | Ongoing   |
| **Card Sorting**    | Information architecture | 15-30       | 1 week    |
| **Diary Studies**   | Long-term behavior       | 10-20       | 2-4 weeks |

See [Customer Research Methods](./references/customer-research-methods.md) for detailed interview frameworks, persona templates, and usability testing protocols.

## Product Analytics

### Key Metrics Framework

```
PIRATE METRICS (AARRR):

ACQUISITION:
- How do users find us?
- Metrics: Traffic, signups, installs

ACTIVATION:
- First positive experience
- Metrics: Onboarding completion, first value

RETENTION:
- Do they come back?
- Metrics: DAU/MAU, cohort retention

REVENUE:
- Do they pay?
- Metrics: Conversion, ARPU, LTV

REFERRAL:
- Do they tell others?
- Metrics: NPS, referral rate, viral coefficient
```

### Product Health Metrics

| Metric               | Formula                           | Target   |
| -------------------- | --------------------------------- | -------- |
| **DAU/MAU**          | Daily users / Monthly users       | 20-50%+  |
| **Activation Rate**  | Completed setup / Signups         | 40-60%+  |
| **Feature Adoption** | Users using feature / Total users | Varies   |
| **Time to Value**    | Days to first value               | Minimize |
| **Power Users**      | Heavy users / Total users         | 15-25%   |

See [Analytics and Experimentation](./references/analytics-and-experimentation.md) for detailed cohort analysis, retention benchmarks, and event tracking strategies.

## A/B Testing

### Experiment Framework

```
EXPERIMENT DESIGN:

HYPOTHESIS:
If we [change], then [metric] will [improve/decrease] because [rationale].

METRICS:
- Primary: The metric you're trying to move
- Secondary: Other metrics to monitor
- Guardrails: Metrics that shouldn't degrade

SAMPLE SIZE:
Use calculator based on:
- Baseline conversion rate
- Minimum detectable effect (MDE)
- Statistical significance (usually 95%)
- Power (usually 80%)

DURATION:
- At least 1 business cycle
- Adequate sample size
- Account for novelty effects
```

### Decision Framework

- **Ship**: Stat sig + practical sig + no negative guardrails
- **Iterate**: Directionally positive but not stat sig, or mixed results
- **Kill**: No effect or negative impact
- **Investigate**: Unexpected results, large variance, segment differences

See [Analytics and Experimentation](./references/analytics-and-experimentation.md) for detailed statistical concepts, common pitfalls, and segmentation analysis.

## Product Launches

### Launch Checklist

```
PRE-LAUNCH:
- [ ] Feature complete and tested
- [ ] Documentation ready
- [ ] Support team trained
- [ ] Marketing materials prepared
- [ ] Sales team enabled
- [ ] Beta feedback incorporated
- [ ] Success metrics defined

LAUNCH:
- [ ] Staged rollout plan
- [ ] Monitoring dashboards live
- [ ] War room established
- [ ] Communication sent
- [ ] Feature flags enabled

POST-LAUNCH:
- [ ] Monitor metrics and feedback
- [ ] Address critical issues
- [ ] Gather early learnings
- [ ] Celebrate wins
- [ ] Retrospective scheduled
```

### Go-to-Market Plan

| Element               | Description                  |
| --------------------- | ---------------------------- |
| **Target Segment**    | Who is this for?             |
| **Value Proposition** | Why will they care?          |
| **Pricing**           | How will we charge?          |
| **Distribution**      | How will they get it?        |
| **Messaging**         | What will we say?            |
| **Enablement**        | How will teams sell/support? |
| **Measurement**       | How will we track success?   |

## Product Discovery

### Discovery Techniques

| Technique               | Purpose              | When to Use       |
| ----------------------- | -------------------- | ----------------- |
| **Opportunity Mapping** | Identify problems    | Early discovery   |
| **Story Mapping**       | Visualize journeys   | Planning releases |
| **Design Sprints**      | Rapid prototyping    | Big bets          |
| **Fake Door Tests**     | Validate demand      | Before building   |
| **Wizard of Oz**        | Test concepts        | Complex features  |
| **Concierge MVP**       | Manual service first | New markets       |

### Opportunity Assessment

```
OPPORTUNITY CANVAS:

PROBLEM:
What problem are we solving?
Who has this problem?
How do they solve it today?

EVIDENCE:
What data supports this?
Customer quotes/feedback?
Market research?

SOLUTION:
What are we proposing?
Why will it work?
What's the MVP?

ASSUMPTIONS:
What must be true?
What risks exist?
How will we validate?

OUTCOME:
Success metrics?
Business impact?
Customer impact?
```

## Deliverable Templates

### PRD Structure (One-Pager)

```
1. EXECUTIVE SUMMARY (3-4 sentences)
- What: One-line description
- Why: Core problem being solved
- Who: Target users
- Success: How we'll measure it

2. BACKGROUND & CONTEXT
- Current situation and pain points
- Supporting data
- Strategic alignment

3. GOALS & SUCCESS METRICS
- Primary goal and success metric
- Secondary goals and metrics
- Guardrail metrics

4. USER STORIES
Format: "As a [persona], I want to [action], so that [benefit]"
- Acceptance criteria
- Priority (Must/Should/Could Have)

5. SOLUTION OVERVIEW
- High-level description
- Key user flows
- Out of scope

6. DESIGN & TECHNICAL CONSIDERATIONS
- Mockups/wireframes
- Dependencies
- Scalability

7. LAUNCH PLAN
- Rollout strategy
- Success criteria
- Risk mitigation

8. OPEN QUESTIONS
- Unresolved decisions
- Areas needing research
```

## Additional Resources

For comprehensive product management frameworks and methodologies:

- [Product Strategy Expert](./references/product-strategy-expert.md) - Complete PM reference guide
- [Customer Research Methods](./references/customer-research-methods.md) - Interview frameworks, personas, usability testing
- [Analytics and Experimentation](./references/analytics-and-experimentation.md) - Retention analysis, A/B testing, event tracking

## See Also

- [Data Science](../data-science/SKILL.md) - Analytics and ML
- [Marketing](../marketing/SKILL.md) - Go-to-market strategy
- [Business Strategy](../business-strategy/SKILL.md) - Strategic planning

© travisjneuman · MIT · travisjneuman/.claude

Similar skills

All skills for Notes, tasks and projects →

From the same set117

The whole set →
react-native This Claude Code skill supports React Native and Expo work on iOS and Android apps. It activates for JavaScript or TypeScript projects involving native features or mobile performance. CX Codex +1 157installs generic-fullstack-code-reviewer generic-fullstack-code-reviewer is a Claude Code skill for reviewing full-stack changes before commits and during pull request reviews. It checks Next.js and NestJS code for bugs, security issues, and project-rule mismatches. CX Codex +1 157installs seo-analytics-auditor seo-analytics-auditor — a skill that checks meta tags, structured data, analytics scripts and Core Web Vitals on a page. It reads the source HTML and walks through the SEO checklist item by item. CX Codex +1 156installs financial-scenario-planner financial-scenario-planner runs a financial plan through bear, base and bull cases, then adds sensitivity tables, break-even and a runway check. Useful when the assumptions behind a model need testing. CX Codex +1 156installs agent-teams Teaches Claude how to compose agent teams: which tasks split well, how many teammates to spawn, and what goes into each spawn prompt. Active only once teams are enabled. CX Codex +1 153installs generic-fullstack-ux-designer generic-fullstack-ux-designer is a Claude Code skill that guides UX design for Next.js and NestJS apps, covering loading states, optimistic UI, forms, and SSR quirks. CX Codex +1 153installs fundraising-analyzer The fundraising-analyzer skill breaks down nonprofit fundraising with donor segments, campaign ROI, retention metrics, and trend views. Use it to review results or plan campaigns. CX Codex +1 153installs microservices-architecture The microservices-architecture Claude Code skill guides microservice design, monolith decomposition, and service communication choices. It activates for distributed-system design tasks. CX Codex +1 153installs

Project sponsors

Companies that keep this analytics open