Rank features by RICE scoring
feature-prioritizerskillsetup L1★103
hamzafarooq/claude-code-starter ↗What it does
Score features by RICE and rank priorities
Best for
Deciding which features to build next when you have a backlog and want a repeatable scoring framework that works across teams.
Inputs
- · feature list
- · timeframe (1 quarter, 1 sprint, 1 year)
- · committed/non-negotiable items
Outputs
- · prioritized table (Feature|Reach|Impact|Confidence|Effort|RICE|Priority)
- · build order rationale
- · cut/defer list
Preconditions
Feature list is pasted or referenced; user can estimate Reach (users/period), Impact (0.25-3 scale), Confidence (%), Effort (person-months)
Failure modes
Feature list too vague; estimates missing for key fields; timeframe not specified; Effort estimates are unreliable (too wide variance)
Trust signals
- · Uses RICE formula (Reach × Impact × Confidence) / Effort
- · Flags assumptions and uncertainty
- · Produces explicit build-order rationale
- · Distinguishes strategic factors not captured in scores