prioritization

Prioritize feature backlogs using RICE scoring, MoSCoW bucketing, and opportunity solution trees.

11|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/qa-aman/next-leap-claude-code --skill prioritization-qa-aman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prioritization
Source: https://github.com/qa-aman/next-leap-claude-code/tree/main/.claude/skills/prioritization
Command: npx skills add https://github.com/qa-aman/next-leap-claude-code --skill prioritization-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often struggle to decide what to build first, defaulting to gut feel or stakeholder pressure instead of structured evaluation. This Skill applies proven prioritization frameworks to rank backlogs objectively and tie decisions to business outcomes. ## Core Features & Use Cases - Opportunity vs Solution Separation: Sorts backlog items into unmet user needs (opportunities) and specific builds (solutions) before scoring, following Teresa Torres's Continuous Discovery Habits approach. - RICE Scoring: Calculates Reach, Impact, Confidence, and Effort scores with stated assumptions for each opportunity. - MoSCoW Alignment: Converts RICE results into Must/Should/Could/Won't buckets for stakeholder communication, with forced constraints to prevent everything being labeled critical. - Use Case: You have 15 feature ideas for next quarter. The Skill separates opportunities from solutions, scores each with RICE, flags low-confidence assumptions, and delivers a clear recommendation of the top 3 items tied to a business outcome. ## Quick Start Ask the assistant to prioritize your feature backlog using RICE scoring and MoSCoW, listing the items you want ranked.

Frequently Asked Questions about prioritization

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

FAQPage Schema
How do I prioritize a product feature backlog?▼

Separate items into opportunities (unmet user needs) and solutions, then score each opportunity with RICE: Reach times Impact times Confidence divided by Effort. Use the scores to inform MoSCoW bucketing and recommend top items tied to a business outcome.

What is RICE scoring in product management?▼

RICE is a prioritization formula: (Reach x Impact x Confidence) / Effort. Reach is users affected per period, Impact uses a 0.25 to 3 scale, Confidence is 100/80/50 percent, and Effort is measured in person-weeks.

RICE vs MoSCoW: which prioritization method should I use?▼

Use both together. RICE provides quantitative scoring to rank opportunities objectively, while MoSCoW translates those scores into Must/Should/Could/Won't buckets that stakeholders can align on. RICE informs the ranking; MoSCoW communicates it.

What is an opportunity solution tree?▼

An opportunity solution tree maps a desired business outcome at the top, branches into opportunities (unmet user needs), and then into possible solutions under each opportunity. It prevents teams from locking into one solution before exploring alternatives.

When should I not use RICE scoring?▼

Avoid treating RICE scores as facts when confidence is low and assumptions are untested. The method works poorly if scores are presented without stated assumptions or if items are not connected to a measurable business outcome.