capability-prioritization

Scores and ranks product capabilities using RICE, MoSCoW, Value vs Complexity, and Kano frameworks.

Updated Jul 13, 2026

Search Tags:#prioritization #product roadmap #rice #moscow #mvp planning #kano model #feature scoring

Ready to run

npx skills add https://github.com/eencinasq/cripto-pos --skill capability-prioritization-eencinasq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: capability-prioritization
Source: https://github.com/eencinasq/cripto-pos/tree/main/.kiro/skills/capability-prioritization
Command: npx skills add https://github.com/eencinasq/cripto-pos --skill capability-prioritization-eencinasq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams struggle to decide which capabilities to build first when facing competing stakeholder demands and limited resources. This Skill applies four established prioritization frameworks to produce a defensible, data-informed ranking instead of relying on gut feel. ## Core Features & Use Cases - Multi-Framework Scoring: Applies RICE (Reach × Impact × Confidence / Effort), MoSCoW (Must/Should/Could/Won't), Value vs Complexity quadrants, and the Kano model to every capability. - Wave Planning: Groups ranked capabilities into MVP, Post-MVP, and Future waves for roadmap sequencing. - Confidence Scoring: Rates the reliability of the prioritization from 1.0 (data-backed) down to below 0.8 (too many unknowns). - Use Case: A product manager with 15 candidate features for a payments app uses this Skill to score each one, identify quick wins and time sinks, and produce a wave plan for the next two quarters. ## Quick Start Prioritize my list of product capabilities using RICE, MoSCoW, Value vs Complexity, and Kano, then produce a wave plan.

Frequently Asked Questions about capability-prioritization

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

FAQPage Schema

How do I prioritize product features with RICE scoring?▼

RICE scoring multiplies Reach (1-10), Impact (0.5-3), and Confidence (20%-100%), then divides by Effort in person-weeks (0.5-10). Higher scores indicate capabilities delivering more value per unit of work, ranking them earlier in the roadmap.

What is the difference between MoSCoW and RICE prioritization?▼

MoSCoW categorizes features into Must, Should, Could, and Won't buckets based on criticality, while RICE produces a numeric score from reach, impact, confidence, and effort. Using both together gives categorical clarity plus quantitative ranking.

How does the Value vs Complexity quadrant work?▼

Capabilities with value above 7 and complexity below 4 are Quick Wins to do first. High value with high complexity are Strategic Bets, low value with low complexity are Fill-ins, and low value with high complexity are Time Sinks to avoid.

When should I use the Kano model for feature prioritization?▼

Use the Kano model to classify features as Basic, Performance, Excitement, Indifferent, or Reverse based on customer satisfaction impact. It complements scoring frameworks by revealing which features users expect versus which delight them.

What does a low confidence score mean in prioritization?▼

A confidence score below 0.8 means too many inputs are unknowns or guesses, so the ranking is unreliable. Scores of 1.0 indicate fully data-backed inputs, while 0.8-0.9 reflect reasonable estimates with some educated guesses.