rice-strats
Researches and calculates RICE prioritization scores for Jira strategy tickets.
Install
mkdir -p .claude/skills/rice-strats && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12364" && unzip -o skill.zip -d .claude/skills/rice-strats && rm skill.zipInstalls to .claude/skills/rice-strats
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
RICE-score RHAISTRAT or RHOAISTRAT Feature tickets in Jira. Researches each ticket's description, strategy attachments, review docs, linked RFEs, and comments, then sets Reach/Impact/Confidence/Effort fields and posts a justification comment. Use this skill whenever the user wants to set RICE scores, prioritize strats, score features, rank RHAISTRAT tickets, or says things like "RICE score these tickets", "set RICE for RHAISTRAT-XXXX", "prioritize these strats", "score the children of RHAISTRAT-XXXX", or provides a list of RHAISTRAT/RHOAISTRAT ticket keys to be scored. Also use when the user mentions "RICE" in the context of Jira strategy tickets.Key capabilities
- →RICE-score Jira strategy Feature tickets
- →Research ticket descriptions, attachments, and comments
- →Set Reach/Impact/Confidence/Effort fields in Jira
- →Post justification comments for RICE scores
- →Prioritize strategy tickets based on RICE framework
How it works
The skill researches Jira tickets, calculates RICE scores based on a rubric and calibration data, and then submits the scores and justifications to Jira after user approval.
Inputs & outputs
When to use rice-strats
- →Prioritizing feature backlogs
- →Scoring RHAISTRAT tickets
- →Automating RICE framework calculations
About rice-strats
Assesses Jira tickets by reviewing attached strategies, comments, and RFEs. It calculates and updates RICE fields to help product managers prioritize features based on evidence.
>-
When not to use it
- →For Jira tickets that are not RHAISTRAT or RHOAISTRAT Feature tickets
- →When the user does not want to set RICE scores
- →When not prioritizing strategy tickets
Limitations
- →Specific to RHAISTRAT or RHOAISTRAT Feature tickets in Jira
- →Requires `JIRA_USER` and `JIRA_TOKEN` environment variables for API access
- →Relies on `references/rice-rubric.md` for scoring scales and guidance
How it compares
This automates a detailed, evidence-based RICE scoring process for Jira tickets, unlike manual, subjective prioritization.
Compared to similar skills
rice-strats side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| rice-strats (this skill) | 0 | 3mo | Review | Advanced |
| task-master | 22 | 6mo | Review | Intermediate |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
task-master
sfc-gh-dflippo
AI-powered task management for structured, specification-driven development. Use this skill when you need to manage complex projects with PRDs, break down tasks into subtasks, track dependencies, and maintain organized development workflows across features and branches.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
agile-product-owner
davila7
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
writing-plans
obra
Use when you have a spec or requirements for a multi-step task, before touching code
feature-design-assistant
davila7
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.