How to Use the `prioritization-frameworks` Skill to Select the Right Framework for Your Backlog

The prioritization-frameworks skill is a built-in reference guide that matches your backlog characteristics to one of nine prioritization methods, providing formulas, decision flows, and ready-to-use templates.

The prioritization-frameworks skill in the phuryn/pm-skills repository helps product managers eliminate guesswork when choosing between ICE, RICE, MoSCoW, and other frameworks. By analyzing your backlog size, product stage, and strategic goals against a curated decision matrix stored in pm-execution/skills/prioritization-frameworks/SKILL.md, this interactive reference ensures you apply the right scoring method for transparent, data-driven prioritization.

Invoking the prioritization-frameworks Skill

You can invoke the skill from any CLI or chat interface that supports pm-skills commands. When called, the skill returns a concise comparison table of nine frameworks: Opportunity Score, ICE, RICE, MoSCoW, Kano, Eisenhower Matrix, Impact vs Effort, Risk vs Reward, and Weighted Decision Matrix.

Each entry includes:

• Best For: Contextual guidance (e.g., "quick triage" vs. "large-team strategic planning")
• Core Formula: The mathematical decision rule or scoring algorithm
• Template Links: Direct URLs to Google Sheets or PDF templates

According to the source code in pm-execution/skills/prioritization-frameworks/SKILL.md, this reference is designed as a standalone execution-phase tool that other discovery skills—such as those defined in pm-product-discovery/skills/prioritize-features/SKILL.md—can call for framework selection logic.

Matching Frameworks to Backlog Characteristics

Small Backlogs (≤ 50 Items) and Rapid Triage

For mixed-priority lists with fewer than 50 items, the skill recommends ICE (Impact × Confidence × Ease). This formula prioritizes speed over precision, making it ideal for early-stage ideation or weekly sprint planning where data may be sparse.

Large-Scale Strategic Initiatives (50+ Items)

When managing extensive, data-driven backlogs, RICE ((Reach × Impact × Confidence) / Effort) adds a Reach dimension that scales with initiative size. According to the repository’s execution-phase documentation in pm-execution/README.md, this framework prevents high-effort, low-reach features from skewing your roadmap.

Customer-Problem Discovery

If your goal is surfacing high-impact, low-satisfaction needs, the skill points to Opportunity Score (Importance × (1 − Satisfaction)) developed by Dan Olsen. This method is specifically calibrated for customer-problem prioritization rather than feature comparison.

Stakeholder Requirement Negotiation

For roadmap discussions requiring scope negotiation, MoSCoW (Must/Should/Could/Won’t) provides a categorical framework that aligns cross-functional stakeholders without complex calculations.

The Decision Flow Logic

The prioritization-frameworks skill implements a short decision tree to guide selection:

• Need a quantitative score? → Use ICE or RICE for numeric ranking.
• Prioritizing customer problems? → Use Opportunity Score.
• Managing a personal task list? → Use the Eisenhower Matrix.

This logic is embedded in the skill’s response generation, allowing you to re-run the command with updated criteria (e.g., "add risk weighting") if the first framework doesn’t surface the correct ordering.

Accessing Templates and Implementation

Once you select a framework, the skill returns a link to a ready-to-use template. For example, selecting ICE generates a shareable Google Sheets URL that automatically calculates priority scores as you input backlog items.

The template URLs are maintained in pm-execution/skills/prioritization-frameworks/SKILL.md alongside the framework definitions, ensuring you always pull the latest version.

Code Examples and CLI Usage

Invoke the skill from a terminal to view the full framework comparison:

pm prioritize-frameworks

Sample Output:

| Framework | Best For                              | Key Insight |
|-----------|---------------------------------------|-------------|
| Opportunity Score | Customer problems                | Importance × (1-Satisfaction) |
| ICE       | Quick triage of ideas                 | Impact × Confidence × Ease |
| RICE      | Large-scale initiatives               | (Reach × Impact × Confidence) / Effort |
| MoSCoW    | Stakeholder requirement negotiation   | Must/Should/Could/Won't |

Select a specific framework and retrieve its template:

pm prioritize-frameworks --framework ICE --template

Template Response:

https://docs.google.com/spreadsheets/d/1LUfnsPolhZgm7X2oij-7EUe0CJT-Dwr-/edit?usp=sharing

For programmatic usage via API:

from claude import ClaudeClient

client = ClaudeClient()
response = client.run_skill(
    skill="prioritization-frameworks",
    inputs={"backlog_size": 70, "focus": "customer-problems"}
)
print(response["recommended_framework"])

# → "Opportunity Score"

Summary

• The prioritization-frameworks skill in phuryn/pm-skills provides an interactive reference for nine distinct prioritization methods.
• Match ICE to small backlogs (≤ 50 items) and RICE to large-scale initiatives requiring Reach calculations.
• Use Opportunity Score for customer-problem discovery and MoSCoW for stakeholder negotiation.
• Source definitions and template URLs are maintained in pm-execution/skills/prioritization-frameworks/SKILL.md.
• Retrieve ready-to-use templates directly through CLI flags or API calls to eliminate manual setup.

Frequently Asked Questions

What is the difference between ICE and RICE in the prioritization-frameworks skill?

ICE (Impact × Confidence × Ease) is optimized for speed and works best for backlogs under 50 items where rapid triangulation matters more than precision. RICE adds a Reach dimension divided by Effort, making it scalable for large, data-driven backlogs where you need to quantify how many users each initiative affects. According to the source code analysis, ICE suits quick weekly planning while RICE supports quarterly roadmap planning.

How do I access templates after selecting a framework?

After invoking the skill, append the --template flag to your selected framework command (e.g., pm prioritize-frameworks --framework ICE --template). The skill returns a direct link to a Google Sheets or PDF template hosted in the repository’s resource library, as documented in pm-execution/skills/prioritization-frameworks/SKILL.md.

Can I use the prioritization-frameworks skill programmatically?

Yes. The skill exposes an API interface that accepts JSON inputs such as backlog_size and focus area. As shown in the Python examples, you can instantiate a client and call client.run_skill() with skill="prioritization-frameworks" to receive a string recommendation like "Opportunity Score" or "RICE" based on your parameters.

Where is the skill definition stored in the repository?

The complete framework definitions, formulas, and template URLs are located in pm-execution/skills/prioritization-frameworks/SKILL.md. The root README.md provides high-level command references, while pm-product-discovery/skills/prioritize-features/SKILL.md demonstrates how discovery-phase skills link to this execution-phase reference for framework selection logic.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}