prioritization-methods

Apply RICE, ICE, MoSCoW, Kano, and other frameworks to rank initiatives.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill prioritization-methods-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prioritization-methods
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/agents/plugins/ai-pm-copilot/skills/prioritization-methods
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill prioritization-methods-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill helps product leaders and teams make defensible prioritization decisions when faced with too many competing features, limited time, or uncertain impact.

Core Features & Use Cases

  • RICE, ICE, and Value vs Effort: Rank and communicate which initiatives should move first, using either quantitative scoring (RICE) or lighter-weight evaluation (ICE) plus visualization (Value/Effort).
  • MoSCoW and Kano: Scope MVP releases (Must/Should/Could/Won’t) and sequence roadmap bets by distinguishing table-stakes requirements from performance and delight opportunities (Kano).
  • Opportunity (JTBD) and Weighted Scoring: Identify the biggest innovation gaps by comparing importance vs satisfaction (Opportunity) and handle complex trade-offs by scoring features against custom weighted criteria (Weighted Scoring).

Example use: You’re planning a quarterly roadmap with a large backlog and unclear differentiation; use RICE to rank quantitatively, apply Value vs Effort to present trade-offs to leadership, and use MoSCoW to lock a crisp MVP scope.

Quick Start

Ask the AI to prioritize your feature backlog by comparing RICE, and then recommend an MVP scope using MoSCoW with clear assumptions for each item.

Frequently Asked Questions about prioritization-methods

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize my product roadmap when I have too many features and limited time?

RICE scoring prioritizes roadmap initiatives by calculating Reach, Impact, Confidence, and Effort, yielding a quantifiable score to rank features. It helps product teams objectively compare competing bets and justify why one initiative moves before another.

What is the best way to scope an MVP release using prioritization frameworks?

Scoping an MVP release is best achieved using the MoSCoW method, which categorizes features into Must, Should, Could, and Won't have buckets. This locks a crisp scope by distinguishing table-stakes requirements from deferred opportunities.

When should I use the Kano model versus Weighted Scoring for backlog triage?

Use the Kano model during backlog triage to sequence roadmap bets by distinguishing basic table-stakes needs from performance and delight opportunities. Use Weighted Scoring when you need to handle complex trade-offs by evaluating features against custom weighted criteria.

How does the Opportunity framework using JTBD help with feature prioritization?

The Opportunity framework using Jobs-to-be-Done (JTBD) helps feature prioritization by identifying the biggest innovation gaps. It compares the importance of a job versus user satisfaction, highlighting underserved areas where new features will drive the most value.

Can I use ICE scoring for lighter-weight roadmap trade-off communication?

Yes, ICE scoring provides a lighter-weight evaluation for roadmap trade-off communication by assessing Impact, Confidence, and Ease. It is ideal for quick backlog triage when you need to present decisions to leadership without extensive quantitative inputs.