rice
RICE prioritization scoring initiatives by Reach, Impact, Confidence, and Effort. Use for feature prioritization, roadmap planning, or when comparing initiatives objectively.
What this skill does
# RICE Prioritization Scoring Score and rank initiatives using Reach, Impact, Confidence, and Effort to make prioritization decisions more objective. ## Instructions For each initiative, estimate the four RICE factors, calculate the score, and rank them. Be explicit about assumptions behind each estimate. ### Output Format **Context** What are we prioritizing? What's the time horizon for Reach? **Factor Definitions** - **Reach**: [Define for this context, e.g., "users affected per quarter"] - **Impact**: [Define for this context, e.g., "effect on conversion rate"] - **Effort**: [Define unit, e.g., "engineer-weeks"] **Scoring Table** | Initiative | Reach | Impact | Confidence | Effort | RICE Score | |------------|-------|--------|------------|--------|------------| | [Name A] | [#] | [0.25-3] | [%] | [#] | [calculated] | | [Name B] | [#] | [0.25-3] | [%] | [#] | [calculated] | | [Name C] | [#] | [0.25-3] | [%] | [#] | [calculated] | **Ranked Results** 1. **[Highest score]** — RICE: X 2. **[Second]** — RICE: X 3. **[Third]** — RICE: X **Detailed Breakdown** For each initiative: ### [Initiative Name] - **Reach**: [X] — [Assumption: how did you estimate this?] - **Impact**: [X] — [Reasoning for impact level] - **Confidence**: [X%] — [What would increase confidence?] - **Effort**: [X] — [What's included in this estimate?] - **RICE Score**: (R × I × C) / E = [score] **Sensitivity Analysis** Which scores would change significantly if assumptions are wrong? **Recommendation** Based on the scores and analysis: > [What to prioritize and why, including any caveats] **What RICE Doesn't Capture** - Strategic alignment - Dependencies - Team capability gaps - Technical risk ## Scoring Guide **Impact Scale** | Score | Meaning | |-------|---------| | 3 | Massive — core value prop | | 2 | High — significant improvement | | 1 | Medium — noticeable improvement | | 0.5 | Low — minor enhancement | | 0.25 | Minimal — nice to have | **Confidence Scale** | Score | Meaning | |-------|---------| | 100% | High — have data | | 80% | Medium — reasonable estimate | | 50% | Low — mostly guessing | $ARGUMENTS
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.