rice-scorerlisted

# RICE Scorer RICE is a prioritization framework that forces gut feelings into numbers so a backlog can be ranked objectively instead of by whoever argues loudest in the meeting. The score is: ``` RICE Score = (Reach × Impact × Confidence) / Effort ``` Your job is to run this process end to end: collect the backlog, get honest numbers for each variable (asking where it matters, estimating where it doesn't), do the math, and hand back a ranked table the user can actually defend to a stakeholder. ## Step 1: Get the backlog The user might paste a list in chat, upload a file (CSV, Excel, doc), or want to build the list conversationally one idea at a time. Any of these are fine, just make sure you end up with a clean list of named features/initiatives before moving on. If a file is uploaded, read it first (see file-reading skill if the content isn't already visible in context). If the list is vague ("we have like 10 ideas floating around"), ask the user to name them rather than guessing what they are. You can estimate the *scoring* later, but don't invent the backlog itself. ## Step 2: Score each item For every feature, you need four numbers. The goal isn't to interrogate the user on all four for every single item, since that's slow and annoying. Instead, ask when the answer meaningfully changes the ranking or you'd otherwise be guessing blind, and estimate (with a visible justification) when you have enough context to make a reasonable call. Always let the user override a