Official skill · Product
Feature prioritization with RICE
Scores a backlog with RICE or ICE, shows the math per item, tests sensitivity, recommends a cut line for capacity, and flags dependencies. Use it when you have more feature requests than capacity and need to decide what goes first.
AI skill
Have your AI rank your backlog and show the math
14 days free · No card needed
Works in Claude, ChatGPT, and coding agents. On Team and Business, the official skill in your pod updates itself when we improve it.
When to use it
- You have more feature requests than capacity and need to decide what goes first
- Stakeholders disagree on priorities and need a shared, visible method
What you give it
- Backlog or feature list
- Reach, impact, confidence, and effort estimates
- Team capacity (optional)
What you get
A scored ranking table with the math shown, a cut line, sensitivity notes, dependencies, and a build/not-now recommendation.
How it works
- Choose RICE or ICE
- Fix the scales before scoring
- Score each item and show the math
- Test sensitivity
- Map dependencies
- Draw the cut line
- Recommend
Example
What you give it
Q2. Capacity 10 person-weeks. Items: CSV export (reach 400 accounts/quarter, medium impact, data, 1 week); auto reminders (reach 900 from data, high impact, a guess, 4 weeks); read-only seat (reach 150 from customer requests, high, some evidence, 2 weeks); SSO (reach 20, massive, data, 3 weeks, promised in a signed contract).
What you get back (the start of it)
Prioritization: Q2
Method: RICE — usage data gives reach for all items · Capacity: 10 person-weeks (8 after 20% buffer)
Ranking
| Rank | Item | Reach | Impact | Confidence | Effort | Score (math) | Inputs from |
|---|---|---|---|---|---|---|---|
| 1 | CSV export | 400 | 1 | 100% | 1 | 400×1×1.0÷1 = 400 | data |
| 2 | Auto reminders | 900 | 2 | 50% | 4 | 900×2×0.5÷4 = 225 | reach: data; impact: estimate |
| 3 | Read-only seat | 150 | 2 | 80% | 2 | 150×2×0.8÷2 = 120 | requests |
| 4 | SSO | 20 | 3 | 100% | 3 | 20×3×1.0÷3 = 20 | data |
Cut line: SSO (committed, 3) + CSV export (1) + auto reminders (4) = 8 person-weeks
Sensitivity
- Auto reminders: if impact is 1 instead of 2, score becomes 112.5 → falls below read-only seat; stays above the line only if capacity allows.
- CSV export: halving reach gives 200 → still rank 2 or better.
- Read-only seat: doubling reach (from requests) to 300 gives 240 → passes auto reminders and moves above the line.
- SSO: halving reach to 10 gives 10 → committed, so it stays above the line at any score.
The rest of this output, the full steps and the checks the AI runs before it answers are in your pod once you add the skill.
Use this skill in your AIShare it with your team
Add it to an AI Skill Pod and everyone on the team, contractors included, uses the same version from their own AI. Read the best ways to share AI skills with a team
Changelog
- v1.0.1 · · Example: every item in the top 5 (all four here) now has a sensitivity line, adding read-only seat and SSO; the input now names the quarter and where the reminders' reach and the read-only seat's reach come from, as the ranking tags them.
- v1.0.0 · · First release.
Sources
- RICE: Simple prioritization for product managers (Intercom) (read 2026-11-04)
- ICE Scoring | Glossary | ProdPad (read 2026-11-04)