rice-prioritisation
$
npx mdskill add mohitagw15856/pm-claude-skills/rice-prioritisationApply consistent, criteria-based RICE scoring to a list of features or initiatives to produce an objective prioritisation ranking.
SKILL.md
.github/skills/rice-prioritisationView on GitHub ↗
--- name: rice-prioritisation description: "Score and rank 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." --- # RICE Prioritisation Skill Apply consistent, criteria-based RICE scoring to a list of features or initiatives to produce an objective prioritisation ranking. ## 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 estimates** (use the standard scale below) - **Effort estimates** (person-months — from engineering if available) - **Quarter or planning period** ## RICE Definitions (adapt to your context) - **Reach:** Number of users affected per quarter (use actual DAU/MAU data where available) - **Impact:** Effect on your primary metric — use scale: 3=massive, 2=high, 1=medium, 0.5=low, 0.25=minimal - **Confidence:** How certain are we about R and I estimates? 100%=high, 80%=medium, 50%=low - **Effort:** Person-months required across all functions ## RICE Formula RICE Score = (Reach × Impact × Confidence) / Effort ## Process 1. For each initiative provided, gather or estimate R, I, C, E values 2. Flag where estimates are weak and note what data would improve them 3. Calculate RICE score for each 4. Rank highest to lowest 5. Flag any "quick wins" (high RICE score, low effort) and "moonshots" (high impact, high effort) 6. Note dependencies between items that affect sequencing 7. **Validate** — Cross-check: if the top-ranked item surprises the team, investigate whether an estimate is inflated. RICE is a tool, not a verdict. ## Output Structure ### RICE Prioritisation: [Backlog/Quarter] | Initiative | Reach | Impact | Confidence | Effort | RICE Score | Notes | |------------|-------|--------|------------|--------|------------|-------| | [name] | [n] | [score] | [%] | [months] | [score] | [flags] | #### Recommended Sequence [Top 5 initiatives with rationale] #### Quick Wins (high score, low effort) [Items to pick up alongside bigger bets] #### Data Gaps to Address [What information would most improve scoring accuracy] ## Quality Checks - [ ] Every initiative has all four RICE components estimated (even roughly) - [ ] Confidence is 50% for anything without data backing (not 100% as a default) - [ ] Quick wins and moonshots are explicitly called out - [ ] Dependencies that affect sequencing are noted - [ ] Any surprising ranking is investigated before accepting it
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.