agentleFS
Sign inStart free
AdhamxonAdhamxon/claude-code-skills/.claude/skills/prioritization-frameworks/SKILL.md

prioritization-frameworks

Skill2 starsChanged 4 months agoMITView on GitHub

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.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never allow customers to design solutions.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

FrameworkBest ForKey Insight
Eisenhower MatrixPersonal tasksUrgent vs Important — for individual PM task management
Impact vs EffortTasks/initiativesSimple 2×2 — quick triage, not rigorous for strategic decisions
Risk vs RewardInitiativesLike Impact vs Effort but accounts for uncertainty
Opportunity ScoreCustomer problemsRecommended. Importance × (1 − Satisfaction). Normalize to 0–1.
Kano ModelUnderstanding expectationsMust-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing.
Weighted Decision MatrixMulti-factor decisionsAssign weights to criteria, score each option. Useful for stakeholder buy-in.
ICEIdeas/initiativesImpact × Confidence × Ease. Recommended for quick prioritization.
RICEIdeas at scale(Reach × Impact × Confidence) / Effort. Adds Reach to ICE.
MoSCoWRequirementsMust/Should/Could/Won't. Caution: project management origin.

Templates

Further Reading

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free