Agent skill

rice-prioritisation

Scores and ranks product initiatives using the RICE framework. Use when asked to prioritise features, rank a backlog using RICE, score initiatives for quarterly planning, or apply an objective framework to a list of competing ideas. Produces a ranked RICE table with scores, quick wins and moonshot flags, dependency notes, and a recommended sequencing order.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorships scriptsMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill rice-prioritisation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 7 KB
Bundled scripts: yes
Path: skills/rice-prioritisation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# RICE Prioritisation Skill Apply consistent, criteria-based RICE scoring to a list of features or initiatives to produce an objective prioritisation ranking. ## Reads from / Writes to the Brain If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know: - **Read first:** `knowledge/strategy.md` (so the ranking serves the direction), the items as `entities/`, and impact `hypotheses/`. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<initiative theme>"` and carry each fact's provenance tag through — an impact estimate is usually a `[hunch]`, not `[data]`. - **📥 Propose to the Brain:** after producing, propose recording the ranking decision to `decisions/` and the reach/impact estimates as `hypotheses/` tagged by evidence strength. Show them, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default). ## Required Inputs Ask the user for these if not provided: - **List of initiatives or features to score** (names and brief descriptions) - **Reach estimates** (users affected per quarter — from analytics if available) - **Impact

What's inside
Steps it walks through
  1. Reads from / Writes to the Brain
  2. Required Inputs
  3. RICE Definitions (adapt to your context)
  4. RICE Formula
  5. Programmatic Helper
  6. Deeper Materials
  7. Process
  8. Output Structure
  9. RICE Prioritisation: [Backlog/Quarter]
  10. Scoring Rubric (0–40)
  11. Quality Checks
  12. Anti-Patterns
Ships with 4 files
  • references/estimate-calibration.md
  • references/worked-example.md
  • scripts/rice_calculator.py
  • templates/scoring-worksheet.md
Commands it runs
From a JSON file (confidence accepts 0.8 or 80)
python3 scripts/rice_calculator.py initiatives.json
Or from a CSV with header: name,reach,impact,confidence,effort
python3 scripts/rice_calculator.py initiatives.csv --format csv
Or piped in
echo '[{"name":"Onboarding","reach":5000,"impact":2,"confidence":0.8,"effort":3}]' \
More from pm-claude-skills
All skills →
About this skill
What does the rice-prioritisation skill do?

Scores and ranks product initiatives using the RICE framework. Use when asked to prioritise features, rank a backlog using RICE, score initiatives for quarterly planning, or apply an objective framework to a list of competing ideas. Produces a ranked RICE table with scores, quick wins and moonshot flags, dependency notes, and a recommended sequencing order.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill rice-prioritisation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going