prioritization
/prioritization
Prioritization frameworks — RICE, WSJF, ICE, MoSCoW, and opportunity cost scoring for backlog ranking. Use when prioritizing features, comparing initiatives, justifying roadmap decisions, or evaluating trade-offs between competing work items.
- Author
- yonatangross ↗
- Repository
- orchestkit ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Prioritization frameworks — RICE, WSJF, ICE, MoSCoW, and opportunity cost scoring for backlog ranking. Use when prioritizing features, comparing initiatives, justifying roadmap decisions, or evaluating trade-offs between competing work items.
Original author description
Prioritization frameworks — RICE, WSJF, ICE, MoSCoW, and opportunity cost scoring for backlog ranking. Use when prioritizing features, comparing initiatives, justifying roadmap decisions, or evaluating trade-offs between competing work items.
How it works
- Decision Tree: Which Framework to Use
- RICE
- WSJF
- ICE
- MoSCoW
- Opportunity Cost & Trade-Off Analysis
- Common Pitfalls
- Related Skills
SKILL.md preview
---
name: prioritization
compatibility: "Claude Code 2.1.277+"
description: "Prioritization frameworks — RICE, WSJF, ICE, MoSCoW, and opportunity cost scoring for backlog ranking. Use when prioritizing features, comparing initiatives, justifying roadmap decisions, or evaluating trade-offs between competing work items."
user-invocable: false
disable-model-invocation: false
metadata:
owner-agent: "product-strategist"
category: document-asset-creation
version: "1.0.0"
author: "OrchestKit"
complexity: "medium"
tags: "rice, wsjf, ice, moscow, prioritization, backlog, scoring, ranking"
allowed-tools: "Read Glob Grep WebFetch WebSearch"
---
# Prioritization Frameworks
Score, rank, and justify backlog decisions using the right framework for the situation.
## Decision Tree: Which Framework to Use
```
Do you have a hard deadline or regulatory pressure?
YES → WSJF (Cost of Delay drives sequencing)
NO → Do you have reach/usage data?
YES → RICE (data-driven, accounts for user reach)
NO → Are you in a time-boxed planning session?
YES → ICE (fast, 1-10 scales, no data required)
NO → Is this a scope negotiation with stakeholders?
YES → MoSCoW (bucket features, control scope creep)
NO → Value-Effort Matrix (quick 2x2 triage)
```
| Framework | Best For | Data Required | Time to Score |
|-----------|----------|---------------|---------------|
| RICE | Data-rich teams, steady-state prioritization | Analytics, user counts | 30-60 min |
| WSJF | SAFe orgs, time-sensitive or regulated work | Relative estimates only | 15-30 min |
| ICE | Startup speed, early validation, quick triage | None | 5-10 min |
| MoSCoW | Scope negotiation, release planning | Stakeholder input | 1-2 hours |
| Value-Effort | 2x2 visual, quick team alignment | None | 10-15 min |
---
## RICE
```
RICE Score = (Reach × Impact × Confidence) / Effort
```
| Factor | Scale | Notes |
|--------|-------|-------|
| Reach | Actual users/quarter | Use analytics; do not estimate |
| Impact | 0.25 / 0.5 / 1 / 2 / 3 | Minimal → Massive per user |
| Confidence | 0.3 / 0.5 / 0.8 / 1.0 | Moonshot → Strong data |
| Effort | Person-months | Include design, eng, QA |
```markdown
## RICE Scoring: [Feature Name]
| Feature | Reach | Impact | Confidence | Effort | Score |
|-------------|--------|--------|------------|--------|--------|
| Smart search| 50,000 | 2 | 0.8 | 3 | 26,667 |
| CSV export | 10,000 | 0.5 | 1.0 | 0.5 | 10,000 |
| Dark mode | 30,000 | 0.25 | 1.0 | 1 | 7,500 |
```
See [rules/prioritize-rice.md](rules/prioritize-rice.md) for ICE, Kano, and full scale tables.
---
## WSJF
```
WSJF = Cost of Delay / Job Size
Cost of Delay = User Value + Time Criticality + Risk Reduction (1-21 Fibonacci each)
```
Higher WSJF = do first. Fibonacci scale (1, 2, 3, 5, 8, 13, 21) forces relative sizing.
```markdown
## WSJF: GDPR Compliance Update
User Value: 8 (required for EU customers)
Time Criticality: 21 (regulatory deadline this quarter)
Risk Reduction: 13 (avoids significant fines)
Job Size: 8 (medium complexity)
Cost of Delay = 8 + 21 + 13 = 42
WSJF = 42 / 8 = 5.25
```
See [rules/prioritize-wsjf.md](rules/prioritize-wsjf.md) for MoSCoW buckets and practical tips.
See [references/wsjf-guide.md](references/wsjf-guide.md) for the full scoring guide.
---
## ICE
```
ICE Score = Impact × Confidence × Ease (all factors 1-10)
```
No user data required. Score relative to other backlog items. Useful for early-stage products and rapid triage sessions.
---
## MoSCoW
Bucket features before estimation. Must-Haves alone should ship a viable product.
```markdown
## Release 1.0 MoSCoW
### Must Have (~60% of effort)
- [ ] User authentication
- [ ] Core CRUD operations
### Should Have (~20%)
- [ ] Search, export, notifications
### Could Have (~20%)
- [ ] Dark mode, keyboard shortcuts
### Won't Have (documented out-of-scope)
- Mobile app (Release 2.0)
- AI features (Release 2.0)
```
---
## Opportunity Cost & Trade-Off Analysis
When two items compete for the same team capacity, quantify what delaying each item costs per month.
```markdown
## Trade-Off: AI Search vs Platform Migration (Q2 eng team)
### Option A: AI Search
- Cost of Delay: $25K/month (competitive risk)
- RICE Score: 18,000
- Effort: 6 weeks
### Option B: Platform Migration
- Cost of Delay: $5K/month (tech debt interest)
- RICE Score: 4,000
- Effort: 8 weeks
### Recommendation
Human decides. Key factors:
1. Q2 OKR: Increase trial-to-paid conversion (favors AI Search)
2. Engineering capacity: Only one team, sequential not parallel
3. Customer commitment: No contractual deadline for either
```
See [rules/prioritize-opportunity-cost.md](rules/prioritize-opportunity-cost.md) for the Value-Effort Matrix and full trade-off template.
See [references/rice-scoring-guide.md](references/rice-scoring-guide.md) for detailed RICE calibration.
---
## Common Pitfalls
| Pitfall | Mitigation |
|---------|------------|
| Gaming scores to justify pre-decided work | Calibrate as a team; document assumptions |
| Mixing frameworks in one table | Pick one framework per planning session |
| Only tracking high-RICE items; ignoring cost of delay | Combine RICE with explicit delay cost analysis |
| MoSCoW Must-Have bloat (>70% of scope) | Must-Haves alone must ship a viable product |
| Comparing RICE scores across different goals | Only compare within the same objective |
---
## Related Skills
- `product-frameworks` — Full PM toolkit (value prop, market sizing, competitive analysis, user research, business case)
- `write-prd` — Convert prioritized features into product requirements documents
- `product-analytics` — Define and instrument the metrics that feed RICE reach/impact scores
- `okr-design` — Set the objectives that determine which KPIs drive RICE impact scoring
- `market-sizing` — TAM/SAM/SOM analysis that informs strategic priority
- `competitive-analysis` — Competitor context that raises or lowers WSJF time criticality scores
---
**Version:** 1.0.0
Files in this package (8)
- SKILL.md 6 KB
- test-cases.json 2 KB
- references/rice-scoring-guide.md 3 KB
- references/wsjf-guide.md 3 KB
- rules/_sections.md 1 KB
- rules/prioritize-opportunity-cost.md 5 KB
- rules/prioritize-rice.md 4 KB
- rules/prioritize-wsjf.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · yonatangross/orchestkit | 100 | MIT |
| The-Utopia-Studio/skills | 100 | Apache-2.0 |
| qa-aman/claude-skills | 100 | MIT |
| ysskrishna/ai-agent-skills | 100 | MIT |
| tarunccet/pm-skills | 100 | MIT |
| jacob-balslev/skill-graph | 100 | Apache-2.0 |
| viktorbezdek/skillstack | 100 | MIT |
| nahid-sparktales/agent-dispatcher | 90 | MIT |
Identical content appears in 2 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 24fd32149d9c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100prioritization-frameworks
Pick a prioritization method and rank a backlog: RICE, ICE, opportunity, MoSCoW and weighted scoring, plus four reference-only methods. Use when ranking features, problems or initiatives against each other. - 90prioritization-frameworks
Use when the user is prioritizing a backlog, building a roadmap, cutting scope, or arguing about what to build next. Trigger phrases include "what should we build first?", "help me cut this list", "I need to defend my roadmap", "should we do X or Y?". Surfaces the right… - 95prioritization-frameworks
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work. - 100feature-prioritization
RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions. - 100prioritize
Feature and initiative prioritization using 7 frameworks (RICE, ICE, WSJF, MoSCoW, Value/Effort, Kano, Weighted Scoring). Auto-detects mode: stack rank, scoring, opportunity assessment, trade-off analysis, or scope cut. Triggers on: "prioritize", "rank these features", "RICE… - 100product-strategy
Use this skill when defining product vision, building roadmaps, prioritizing features, or choosing frameworks like RICE, ICE, or MoSCoW. Triggers on product vision, roadmapping, prioritization, RICE scoring, product strategy, feature prioritization, OKRs for product, and any…