skills.rest
slgoodrich
slgoodrichCOMMUNITY
Explore all skills by this author →
GitHub

prioritization-methods

Prioritize features using RICE, ICE, MoSCoW, Kano, and weighted scoring frameworks.

121|19|Updated Oct 17, 2025
Search Tags:#product management#ICE scoring#prioritization#Kano model#product backlog#RICE scoring#MoSCoW
One-click install
npx skills add https://github.com/slgoodrich/agents --skill prioritization-methods
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prioritization-methods
Source: https://github.com/slgoodrich/agents/tree/main/plugins/product-management/skills/prioritization-methods
Command: npx skills add https://github.com/slgoodrich/agents --skill prioritization-methods

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the problem of ineffective prioritization by providing a suite of proven methodologies. It helps product leaders objectively rank features, initiatives, and bugs, ensuring focus on the highest-value work to maximize product impact and achieve strategic goals, avoiding feature bloat and misaligned efforts.

Core Features & Use Cases

  • RICE & ICE Scoring: Quantify reach, impact, confidence, and effort for objective ranking.
  • MoSCoW Prioritization: Categorize features as Must, Should, Could, or Won't Have for scope management.
  • Kano Model: Understand customer satisfaction levels for features (delighters, performance, basic).
  • Value/Effort Matrix: Visualize and prioritize initiatives based on perceived value and required effort.
  • Weighted Scoring: Customize criteria for objective ranking based on strategic importance.
  • Use Case: Prioritize a backlog of 20 new features for a mobile app using the RICE scoring model, providing a ranked list and justification for each to align the development roadmap.

Quick Start

Prioritize a backlog of 20 new features for a mobile app using the RICE scoring model, providing a ranked list and justification for each.

Frequently Asked Questions about prioritization-methods

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

FAQPage Schema
How do I prioritize features using RICE scoring?▼

RICE scoring prioritizes features by quantifying Reach (users affected), Impact (effect per user), Confidence (certainty level), and Effort (time to build). Divide Reach × Impact × Confidence by Effort to rank initiatives objectively and align development roadmaps with strategic value.

What's the difference between RICE, ICE, and MoSCoW prioritization methods?▼

RICE and ICE scoring use quantitative formulas for ranking; ICE excludes Reach. MoSCoW categorizes features as Must, Should, Could, or Won't Have for scope management. Choose RICE/ICE for numeric comparison across backlog items; use MoSCoW for release scoping and stakeholder alignment.

How do I use the Kano model to understand customer satisfaction?▼

The Kano model categorizes features into basic needs (expected), performance factors (competitive advantage), and delighters (unexpected positives). Map backlog items to these categories to identify which features drive satisfaction, prevent dissatisfaction, or differentiate your product.

Can I prioritize a product backlog with weighted scoring?▼

Yes. Weighted scoring customizes criteria (revenue impact, strategic alignment, technical risk) and assigns weights reflecting business priorities. Score each feature against criteria, multiply by weights, and sum to rank initiatives based on your organization's specific goals.

How do I create a value versus effort matrix for prioritization?▼

Plot initiatives on a grid with perceived value on one axis and required effort on the other. Prioritize high-value, low-effort items first, then tackle high-value, high-effort work. This visual approach makes trade-offs transparent across product teams and aligns stakeholders.

What are the limitations of prioritization frameworks?▼

Scoring frameworks depend on estimation accuracy and can mask political disagreements. Confidence scores are subjective; effort estimates drift as scope clarifies. Use frameworks as decision aids, not absolutes—validate rankings through stakeholder review and adjust as new information emerges.

Related Skills

Explore More Product & Management Skills→
assimovtassimovt
54

feature-prioritization

Prioritize product features using RICE scoring and blocker versus enabler classification.

Community
Intermediate
roberttmadsen13-delroberttmadsen13-del

roadmap-planning

Translate business goals and constraints into a sequenced roadmap with prioritized epics.

Community
Advanced
kevinlinkevinlin
14

roadmap-management

Plan and prioritize product roadmaps using RICE, MoSCoW, and ICE frameworks.

Community
Advanced
MatrixFounderMatrixFounder
4

skill-product-backlog-prioritization

Calculate WSJF scores for product backlog items using a Python script.

Community
Intermediate