Prioritization Frameworks
Pick and apply the right prioritization framework (RICE, ICE, Kano, MoSCoW, Opportunity Score, and others) when scoping what to build next.
Overview
prioritization-frameworks is an agent skill most often used in Validate (also Idea research, Build pm, Grow lifecycle) that explains 9 prioritization frameworks with formulas, templates, and selection guidance.
Install
npx skills add https://github.com/phuryn/pm-skills --skill prioritization-frameworksWhat is this skill?
- Reference guide to 9 prioritization frameworks with formulas and when-to-use guidance
- Core principle: prioritize customer problems (opportunities), not features customers design for you
- Opportunity Score (Dan Olsen): Importance × (1 − Satisfaction) with Importance vs Satisfaction plotting
- ICE, RICE, Kano, MoSCoW, and additional frameworks with templates for initiatives and ideas
- Explicit routing for RICE vs ICE and similar framework selection debates
- Opportunity Score uses Importance × (1 − Satisfaction) on a normalized 0–1 scale
Adoption & trust: 1k installs on skills.sh; 12.3k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your backlog is a pile of feature ideas and shouty requests with no shared method to rank which customer problems matter most.
Who is it for?
Solo founders and small teams deciding scope before coding or choosing between RICE, ICE, Kano, and MoSCoW.
Skip if: Teams that already have a locked portfolio process with executive-weighted OKRs and no appetite for framework education.
When should I use this skill?
Selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
What do I get? / Deliverables
You select a framework (for example Opportunity Score or RICE), score opportunities with documented formulas, and align the team on what to build next.
- Chosen framework with filled formula template (RICE, ICE, Opportunity Score, etc.)
- Prioritized opportunity list ranked by problems not solution requests
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Validate → scope because the reference is used while narrowing which customer problems deserve build investment before full implementation. Subphase scope fits comparing frameworks and scoring opportunities when the backlog is still hypothesis-heavy, not post-launch ops tuning.
Where it fits
Score which underserved jobs-to-be-done deserve a prototype before you commit a domain name.
Run Opportunity Score surveys and plot Importance vs Satisfaction to pick MVP slice.
Apply RICE to rank engineering tasks for the next two-week agent-assisted sprint.
Re-prioritize retention fixes versus acquisition experiments using ICE with explicit confidence inputs.
How it compares
Use as a structured PM reference inside the agent, not as a analytics MCP or automated scoring pipeline tied to your production database.
Common Questions / FAQ
Who is prioritization-frameworks for?
Indie builders and product-minded solos who own roadmap calls without a dedicated PM staff.
When should I use prioritization-frameworks?
During Idea research when comparing markets; Validate scope when ranking opportunities; Build pm when grooming sprints; and Grow lifecycle when rebalancing retention work against new bets.
Is prioritization-frameworks safe to install?
It is documentation-only methodology—still review the Security Audits panel on this Prism page before adding any third-party skill to your agent environment.
SKILL.md
READMESKILL.md - Prioritization Frameworks
## Prioritization Frameworks Reference A reference guide to help you select and apply the right prioritization framework for your context. ### Core Principle Never allow customers to design solutions. Prioritize **problems (opportunities)**, not features. ### Opportunity Score (Dan Olsen, *The Lean Product Playbook*) The recommended framework for prioritizing customer problems. Survey customers on **Importance** and **Satisfaction** for each need (normalize to 0–1 scale). Three related formulas: - **Current value** = Importance × Satisfaction - **Opportunity Score** = Importance × (1 − Satisfaction) - **Customer value created** = Importance × (S2 − S1), where S1 = satisfaction before, S2 = satisfaction after High Importance + low Satisfaction = highest Opportunity Score = best opportunities. Plot on an Importance vs Satisfaction chart — upper-left quadrant is the sweet spot. Prioritizes customer problems, not solutions. ### ICE Framework Useful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors. - **I** (Impact) = Opportunity Score × Number of Customers affected - **C** (Confidence) = How confident are we? (1-10). Accounts for risk. - **E** (Ease) = How easy is it to implement? (1-10). Accounts for economic factors. **Score** = I × C × E. Higher = prioritize first. ### RICE Framework Splits ICE's Impact into two separate factors. Useful for larger teams that need more granularity. - **R** (Reach) = Number of customers affected - **I** (Impact) = Opportunity Score (value per customer) - **C** (Confidence) = How confident are we? (0-100%) - **E** (Effort) = How much effort to implement? (person-months) **Score** = (R × I × C) / E ### 9 Frameworks Overview | Framework | Best For | Key Insight | |-----------|----------|-------------| | Eisenhower Matrix | Personal tasks | Urgent vs Important — for individual PM task management | | Impact vs Effort | Tasks/initiatives | Simple 2×2 — quick triage, not rigorous for strategic decisions | | Risk vs Reward | Initiatives | Like Impact vs Effort but accounts for uncertainty | | **Opportunity Score** | Customer problems | **Recommended.** Importance × (1 − Satisfaction). Normalize to 0–1. | | Kano Model | Understanding expectations | Must-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing. | | Weighted Decision Matrix | Multi-factor decisions | Assign weights to criteria, score each option. Useful for stakeholder buy-in. | | **ICE** | Ideas/initiatives | Impact × Confidence × Ease. Recommended for quick prioritization. | | **RICE** | Ideas at scale | (Reach × Impact × Confidence) / Effort. Adds Reach to ICE. | | MoSCoW | Requirements | Must/Should/Could/Won't. Caution: project management origin. | ### Templates - [Opportunity Score intro (PDF)](https://drive.google.com/file/d/1ENbYPmk1i1AKO7UnfyTuULL5GucTVufW/view) - [Importance vs Satisfaction Template — Dan Olsen (Google Slides)](https://docs.google.com/presentation/d/1jg-LuF_3QHsf6f1nE1f98i4C0aulnRNMOO1jftgti8M/edit#slide=id.g796641d975_0_3) - [ICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1LUfnsPolhZgm7X2oij-7EUe0CJT-Dwr-/edit?usp=share_link&ouid=111307342557889008106&rtpof=true&sd=true) - [RICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1S-6QpyOz5MCrV7B67LUWdZkAzn38Eahv/edit?usp=sharing&ouid=111307342557889008106&rtpof=true&sd=true) --- ### Further Reading - [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium) - [Kano Model: How to Delight Your Customers Without Becomi