rice

Score initiatives with RICE inputs and output a ranked list.

35|13|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/wildwasser/opencode-agents --skill rice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rice
Source: https://github.com/wildwasser/opencode-agents/tree/main/.opencode/skills/rice
Command: npx skills add https://github.com/wildwasser/opencode-agents --skill rice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prioritizes initiatives objectively by scoring each option against Reach, Impact, Confidence, and Effort to support data-driven roadmapping and resource allocation.

Core Features & Use Cases

  • RICE scoring: quantify Reach, Impact, Confidence, and Effort to compute a comparative score for each initiative.
  • Prioritization & planning: generate a ranked backlog or roadmap based on calculated scores.
  • Use Case: for a quarterly planning cycle, score proposed features to decide which to implement first and which to deprioritize.

Quick Start

Score your initiatives using the RICE framework and rank them to guide the roadmap.

Frequently Asked Questions about rice

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

FAQPage Schema
What is RICE scoring for product roadmap prioritization?

RICE scoring is a prioritization framework that quantifies initiatives by Reach, Impact, Confidence, and Effort to compute a comparative score. It enables data-driven roadmapping and objective resource allocation across product and engineering teams.

How do I prioritize features using the RICE framework for sprint planning?

To prioritize features for sprint planning, provide explicit estimates for Reach, Impact, Confidence, and Effort. The framework calculates a comparative score for each initiative and outputs a ranked backlog to guide your roadmap decisions.

Can I use RICE scoring for quarterly roadmap planning across engineering teams?

Yes, you can use RICE scoring for quarterly roadmaps. By scoring proposed features against Reach, Impact, Confidence, and Effort, engineering teams can objectively decide which initiatives to implement first and which to deprioritize.

What is the best way to objectively rank product backlog initiatives?

The best way to objectively rank initiatives is applying the RICE framework, which requires explicit estimates for Reach, Impact, Confidence, and Effort. This generates a ranked list with calculated scores and rationale for data-driven decision-making.

What data do I need to calculate RICE scores for feature prioritization?

You need explicit estimates for Reach, Impact, Confidence, and Effort to calculate RICE scores. Providing these quantitative inputs for each proposed initiative allows the framework to compute comparative scores and generate a ranked product backlog.