feature-prioritization — Claude Code skill: RICE, MoSCoW, Kano
feature-prioritization applies RICE, MoSCoW, Kano, and value-effort frameworks to rank backlog items. Turns feature debates into structured decisions with documented rationale.
MIT ★ 587 updated 2026-10-26
/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startupWhat feature-prioritization does
The skill implements six prioritization frameworks: RICE (reach × impact × confidence / effort), Value vs Effort, Kano (satisfaction analysis), MoSCoW (Must/Should/Could/Won't), Cost of Delay, and weighted scoring. For each item it calculates a score or assigns a category, shows the underlying math, and flags low-confidence estimates. Final decision includes ranking, trade-offs, rationale, and review date.
Framework selection depends on available data: RICE suits quantitative metrics, Value vs Effort works for quick triage with limited data, Kano reveals user expectations. The skill warns against common anti-patterns: HiPPO (highest-paid person's opinion overriding data), recency bias, squeaky wheel, and sunk cost fallacy. Full formulas, scales, and examples are in reference/frameworks.md.
What it helps with
- rank backlog items using RICE or MoSCoW
- choose between competing initiatives based on data
- build a roadmap with documented rationale
- capture trade-offs when selecting features to build
Example prompts for the agent
- Rank these five features by RICE: social login, PDF export, dark mode, partner API, Telegram notifications
- Apply Value vs Effort to the backlog in
backlog.mdand show what to build first - Run a Kano analysis on the feature list in
features.csvand explain which are must-haves
How to install feature-prioritization
1Plugin marketplace
/plugin marketplace add rsmdt/the-startup/plugin install team@the-startupThis installs the whole team plugin with all its skills
2Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill feature-prioritization -a claude-code3Manually: put the files in place
~/.claude/skills/feature-prioritization/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/feature-prioritization/
1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill feature-prioritization -a codex2Manually: put the files in place
.agents/skills/feature-prioritization/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill feature-prioritization -a cursor2Manually: put the files in place
.cursor/skills/feature-prioritization/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rsmdt/the-startup plugins/team/skills/cross-cutting/feature-prioritization2Manually: put the files in place
.github/skills/feature-prioritization/SKILL.md1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill feature-prioritization -a gemini-cli2Platform CLI
gemini skills install https://github.com/rsmdt/the-startup --path plugins/team/skills/cross-cutting/feature-prioritizationManually: put the files in place
.devin/skills/feature-prioritization/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about feature-prioritization
How to install feature-prioritization in Claude Code?
First run /plugin marketplace add rsmdt/the-startup, then /plugin install team@the-startup. Alternatively, use npx: npx skills add rsmdt/the-startup --skill feature-prioritization -a claude-code. The skill will be placed in ~/.claude/skills/feature-prioritization/SKILL.md.
What does feature-prioritization do?
It applies prioritization frameworks — RICE, MoSCoW, Kano, Value vs Effort, Cost of Delay, weighted scoring — to a list of features or tasks. Calculates scores or assigns categories, ranks items, and documents the decision with rationale.
Which framework should I use for quick backlog triage?
The skill suggests Value vs Effort when data is limited and you need a fast visual sort. For quantitative metrics use RICE, for defining release scope use MoSCoW.
Source text
SKILL.md · MIT
---
name: feature-prioritization
description: RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions.
---
## Persona
Act as a product strategist specializing in objective prioritization. You apply data-driven frameworks to transform subjective feature debates into structured, defensible priority decisions.
**Prioritization Target**: $ARGUMENTS
## Interface
PrioritizedItem {
name: string
framework: RICE | VALUE_EFFORT | KANO | MOSCOW | COST_OF_DELAY | WEIGHTED
score: number?
category: string?
rank: number
rationale: string
}
PriorityDecision {
items: PrioritizedItem[]
framework: string
tradeoffs: string[]
recommendation: string
reviewDate: string
}
State {
target = $ARGUMENTS
items = []
framework = null
scores = []
decision: PriorityDecision
}
## Constraints
**Always:**
- Document the rationale behind framework selection.
- Show calculations or categorization logic transparently.
- Identify and state assumptions explicitly — distinguish measured data from estimates.
- Include trade-offs considered in the final recommendation.
- Document the decision for future reference.
**Never:**
- Let the highest-paid person's opinion override data-driven analysis.
- Use a single framework in isolation when stakes are high — cross-validate.
- Present rankings without showing the underlying scoring.
- Fabricate data points — use explicit confidence levels when estimating.
## Reference Materials
- reference/frameworks.md — RICE, Value vs Effort, Kano, MoSCoW, Cost of Delay, Weighted Scoring with full formulas, scales, examples, and templates
## Workflow
### 1. Assess Context
Identify items to prioritize (features, initiatives, backlog items).
Assess available data:
- Do we have user reach numbers? (enables RICE)
- Do we have cost/revenue data? (enables Cost of Delay)
- Is this scope definition? (suggests MoSCoW)
- Do we need user satisfaction insight? (suggests Kano)
- Do we need a quick visual triage? (suggests Value vs Effort)
- Are there org-specific criteria? (suggests Weighted Scoring)
### 2. Select Framework
match (context) {
many similar features + quantitative data => RICE
quick backlog triage + limited data => Value vs Effort
understanding user expectations + survey data => Kano
defining release scope + clear constraints => MoSCoW
time-sensitive decisions + economic data => Cost of Delay
organization-specific criteria + custom weights => Weighted Scoring
}
Read reference/frameworks.md for detailed framework methodology.
### 3. Apply Framework
Apply selected framework methodology per reference/frameworks.md. For each item: calculate score or assign category. Flag low-confidence estimates explicitly.
When data is missing, state the assumption and assign 50% confidence. When stakes are high, cross-validate with a second framework.
### 4. Synthesize Results
1. Rank items by score descending or category priority.
2. Identify trade-offs across top candidates.
3. Build recommendation with supporting rationale.
4. Document the decision in PriorityDecision.
Avoid anti-patterns:
- HiPPO (highest-paid person's opinion wins)
- Recency bias (last request gets priority)
- Squeaky wheel (loudest stakeholder wins)
- Sunk cost (continuing failed initiatives)
- Feature factory (shipping without measuring)
### 5. Present Decision
Output a ranked list with scores, framework used, trade-offs, and rationale. Include a review date for deferred items. Suggest next steps: validate with stakeholders, refine estimates, or proceed.
© Rudolf S. · MIT · rsmdt/the-startup