mcpField
P
pm-prioritization

pm-prioritization

github.com/majesticlabs-devProductivity5035 installsUpdated 7w ago
Repository

About pm-prioritization

pm-prioritization is a product-management skill for comparing features and opportunities. It covers RICE and ICE scoring, Opportunity Solution Trees, and common prioritization anti-patterns.

Key features

  1. 01RICE scoring with a comparison table
  2. 02ICE scoring for quicker decisions
  3. 03Opportunity Solution Tree structure
  4. 04Guidance on prioritization anti-patterns

Use cases

  1. 01Rank features using reach, impact, confidence, and effort
  2. 02Make quick, lightweight prioritization decisions
  3. 03Map outcomes to customer opportunities and experiments

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill pm-prioritization

After installing, type/pm-prioritizationin Claude Code to confirm it loaded.

Details

From the project README

Feature Prioritization

Frameworks for prioritizing features and opportunities.

RICE Scoring

RICE Score = (Reach × Impact × Confidence) / Effort
FactorDefinitionScale
ReachUsers affected per quarterActual number
ImpactEffect on users3=Massive, 2=High, 1=Medium, 0.5=Low, 0.25=Minimal
ConfidenceHow sure are you?100%=High, 80%=Medium, 50%=Low
EffortPerson-months to shipActual estimate

RICE Table:

| Feature | Reach | Impact | Confidence | Effort | RICE Score |
|---------|-------|--------|------------|--------|------------|
| [Feature A] | 5000 | 2 | 80% | 2 | 4000 |
| [Feature B] | 1000 | 3 | 50% | 1 | 1500 |

ICE Scoring (Simpler)

ICE Score = Impact × Confidence × Ease
FactorScale
Impact1-10 (potential value)
Confidence1-10 (certainty of impact)
Ease1-10 (implementation simplicity)

ICE Table:

| Feature | Impact | Confidence | Ease | ICE Score |
|---------|--------|------------|------|-----------|
| [Feature A] | 8 | 7 | 5 | 280 |
| [Feature B] | 6 | 9 | 8 | 432 |

Opportunity Solution Tree

Structure:

Outcome (measurable business goal)
├── Opportunity 1 (unmet customer need)
│   ├── Solution 1a
│   │   └── Experiment: [test]
│   └── Solution 1b
│       └── Experiment: [test]
├── Opportunity 2 (another need)
│   └── Solution 2a
│       └── Experiment: [test]
└── Opportunity 3
    └── ...

OST Template:

## Outcome
**Goal:** [Measurable objective]
**Current:** [Baseline metric]
**Target:** [Target metric]
**Timeline:** [By when]

## Opportunity Map

### Opportunity 1: [Customer need/pain point]
**Evidence:** [Interview quotes, data]
**Size:** [How many users affected]

**Solutions considered:**
1. **[Solution A]**
   - Effort: [S/M/L]
   - Experiment: [How to test cheaply]
   - Success metric: [What to measure]

2. **[Solution B]**
   - Effort: [S/M/L]
   - Experiment: [How to test cheaply]
   - Success metric: [What to measure]

**Selected:** [Which and why]

When to Use Each

FrameworkBest ForLimitations
RICELarge teams, many featuresRequires reach data
ICEQuick decisions, small teamsMore subjective
OSTStrategy alignmentRequires outcome clarity

Prioritization Anti-Patterns

  • HiPPO (Highest Paid Person's Opinion) → Use data
  • Squeaky wheel (loudest customer wins) → Weight by segment size
  • Pet projects (internal favorites) → Require evidence
  • Sunk cost (we started, must finish) → Re-evaluate regularly

Comments

Markdown supported