product-prioritization

Name: product-prioritization
Availability: InStock
Author: petrogurcak

Apply RICE, ICE, MoSCoW, and Kano frameworks to prioritize product features.

Updated Aug 27, 2026

Search Tags:#decision making #product management #frameworks #prioritization #backlog grooming #feature ranking

Ready to run

npx skills add https://github.com/petrogurcak/skills --skill product-prioritization-petrogurcak

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-prioritization
Source: https://github.com/petrogurcak/skills/tree/main/plugins/product/skills/product-prioritization
Command: npx skills add https://github.com/petrogurcak/skills --skill product-prioritization-petrogurcak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides structured frameworks to objectively rank product features and make informed decisions about what to build next, moving beyond subjective opinions and gut feelings.

Core Features & Use Cases

Framework Application: Utilizes RICE, ICE, MoSCoW, Kano, and Value vs. Effort matrices for diverse prioritization needs.
Decision Support: Helps resolve stakeholder disagreements and manage overwhelming feature requests.
Use Case: When faced with a backlog of 20 feature ideas and limited development resources, use this Skill to apply the RICE framework and determine the top 3 features that will deliver the most impact.

Quick Start

Use the product-prioritization skill to rank the following features using the RICE framework: Feature A (Reach: 1000, Impact: 3, Confidence: 80%, Effort: 2), Feature B (Reach: 500, Impact: 2, Confidence: 100%, Effort: 1).

Frequently Asked Questions about product-prioritization

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

FAQPage Schema

How do I prioritize product features using the RICE framework?▼

To prioritize product features with the RICE framework, you must define the reach, impact, confidence, and effort for each backlog item to calculate a quantitative score for objective feature ranking.

What is the best way to rank a backlog when stakeholders disagree on what to build?▼

The best way to rank a backlog during stakeholder conflict is applying structured decision-making frameworks like MoSCoW or Kano to objectively categorize features and align product management priorities.

When should I use qualitative prioritization frameworks instead of quantitative ones?▼

You should use qualitative prioritization frameworks like MoSCoW or Kano when you need to categorize features by value rather than calculating specific metrics like reach, impact, confidence, and effort.

How do I manage an overload of feature requests with limited development resources?▼

To manage feature request overload with limited resources, apply the Value vs. Effort matrix or ICE framework to objectively rank backlog items and identify the highest impact features to build next.

Do I need specific data inputs to use quantitative prioritization frameworks like ICE?▼

Yes, quantitative frameworks like ICE require clear definition of impact, confidence, and effort metrics for each feature to objectively prioritize the product backlog and move beyond subjective opinions.