phuryn/prioritization-frameworks
pm-execution/skills/prioritization-frameworks/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add phuryn/pm-skills prioritization-frameworksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 20, 2026, 8:17 AM99.6s1 file scanned
SKILL.md
- name:
- prioritization-frameworks
- description:
- 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.
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)
- Importance vs Satisfaction Template — Dan Olsen (Google Slides)
- ICE Template (Google Sheets)
- RICE Template (Google Sheets)
Further Reading
- The Product Management Frameworks Compendium + Templates
- Kano Model: How to Delight Your Customers Without Becoming a Feature Factory
- Continuous Product Discovery Masterclass (CPDM) (video course)
Related Skills
phuryn/shipping-artifacts
tools
VerifiedTrustedCommunity
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
22,371SKILL.mdUpdated Jun 6, 2026
phuryn/intended-vs-implemented
development
VerifiedTrustedCommunity
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
22,371SKILL.mdUpdated Jun 6, 2026
phuryn/strategy-red-team
testing
VerifiedTrustedCommunity
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
12,047SKILL.mdUpdated Jun 6, 2026
phuryn/review-resume
testing
VerifiedTrustedCommunity
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
7,806SKILL.mdUpdated Mar 20, 2026