prioritization-frameworks

Applies RICE, ICE, WSJF, and value-vs-effort frameworks to rank product backlogs with auditable scoring.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill prioritization-frameworks-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prioritization-frameworks
Source: https://github.com/hero-engine/hero/tree/main/domains/pm/skills/prioritization-frameworks
Command: npx skills add https://github.com/hero-engine/hero --skill prioritization-frameworks-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often rank backlogs on gut feel or quote framework scores as if they were hard data, hiding the guesses behind Reach, Impact, Confidence, and Effort inputs. This Skill provides the mechanics of the four common prioritization frameworks, names when each fits, and forces the assumptions behind every score into the open. ## Core Features & Use Cases - Four framework mechanics: Full formulas, input scales, and fit conditions for RICE, ICE, WSJF, and value-vs-effort 2x2 grids. - Score honesty checks: Named failure modes (reach-as-guess, confidence creep, effort sandbagging) plus mandatory Notes columns recording the basis for every estimate. - Override discipline: A four-step process for disagreeing with a framework result while logging the override in the initiative's rationale field. - Use Case: When ranking 15 candidate initiatives for quarterly planning, use this Skill to produce a RICE table with segment-weighted reach, evidence-anchored confidence, and engineering-signed effort estimates that stakeholders can challenge line by line. ## Quick Start Ask the AI to score and rank your backlog items using RICE with notes explaining each Reach, Impact, Confidence, and Effort estimate.

Frequently Asked Questions about prioritization-frameworks

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

FAQPage Schema
How do I prioritize a product backlog with RICE?▼

RICE scores each item as (Reach × Impact × Confidence) / Effort, producing a sortable column for like-for-like comparison across 10 or more candidates. Always include a Notes column recording where each estimate came from so the team can challenge inputs instead of arguing about outputs.

RICE vs ICE vs WSJF: which prioritization framework should I use?▼

Use RICE for high-volume backlog ranking, ICE for fast intake triage where you bucket rather than rank-order, and WSJF for sequencing committed work where cost of delay and dependencies matter. Use the value-vs-effort 2x2 for stakeholder conversations with 15 or fewer items.

Why do RICE scores mislead product teams?▼

RICE scores mislead when Reach and Impact are guesses but the output prints to two decimals and looks like data. Common failure modes include confidence defaulting to 80 percent, effort estimated without engineering input, and inputs adjusted after ranking to make a favored item win.

How do I handle reach weighting across customer segments?▼

Weight reach by segment importance when segment economics differ materially, using team-agreed weights such as enterprise 5, mid-market 3, SMB 1, free 0.3. Disclose the weighting in the Notes column, since a score that quietly uses weighted reach is worse than one that does not weight at all.

What should I do when the framework ranking conflicts with strategy?▼

Show the framework result first, name the override factor explicitly, and record the override in the initiative's rationale field with a revisit condition. The framework is a sanity check that owns the audit trail; the team owns the actual call.