agentleFS
nisarthnisarth/claude-skills-store/skills/product-management/feature-prioritization/SKILL.md

feature-prioritization

Skill1 starsChanged 7 months agoMITView on GitHub

Prioritize features using structured frameworks: RICE, MoSCoW, ICE, Kano. Score and rank based on impact vs. effort. Use when deciding what to build next from a long list, comparing competing feature requests, justifying a roadmap to stakeholders, or running a prioritization exercise with the team. Trigger phrases: "prioritize features", "RICE scoring", "what should we build first", "rank these features", "MoSCoW analysis", "ICE scoring", "prioritization framework", "impact vs effort", "feature ranking", "Kano analysis", "prioritize backlog"

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Response: Use RICE scoring for a data-driven approach.

    line 158
  2. Distinctive:

    Response: Use ICE for speed. Score each on a 1-10 scale for Impact, Confidence, and Ease.

    line 162
  3. Very specific:

    Response: Use MoSCoW. Categorize each feature as Must/Should/Could/Won't.

    line 166

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Feature Prioritization

Score and rank features using established prioritization frameworks. Compare impact vs. effort, apply structured scoring, and produce defensible priority rankings.

Workflow

Step 1: Gather the Feature List

Collect the candidates:

#FeatureSourceUser SegmentNotes
1[Feature name][Customer request / internal / data][Who benefits][Context]
2[Feature name][Source][Segment][Context]

For each feature, ensure you have enough context to score. If a feature is too vague to estimate impact, break it down or gather more information first.

Step 2: Choose the Framework

Select based on context:

FrameworkBest ForStrengthsLimitations
RICELarge backlogs, data-availableQuantitative, defensibleRequires estimates for each dimension
ICEQuick prioritization, early-stageSimple, fastLess rigorous than RICE
MoSCoWRelease scoping, stakeholder alignmentClear categories, easy to communicateSubjective, no ranking within categories
KanoUnderstanding user satisfactionReveals delight vs. expectationRequires user research data
Value vs. EffortVisual prioritization, team exercisesIntuitive, visualCan oversimplify complex trade-offs

Step 3: Score with the Chosen Framework

RICE Framework

FeatureReachImpactConfidenceEffortRICE Score
[Name][#users/quarter][0.25/0.5/1/2/3][50%/80%/100%][person-months][RIC/E]
  • Reach: How many users will this affect per quarter? Use real numbers.
  • Impact: Minimal (0.25), Low (0.5), Medium (1), High (2), Massive (3)
  • Confidence: Low (50%), Medium (80%), High (100%). Penalizes guesses.
  • Effort: Person-months of engineering, design, and QA work.
  • Score: (Reach x Impact x Confidence) / Effort

ICE Framework

FeatureImpactConfidenceEaseICE Score
[Name][1-10][1-10][1-10][ICE]
  • Impact: How much will this move the target metric? (1 = minimal, 10 = transformative)
  • Confidence: How sure are you about the impact estimate? (1 = guess, 10 = data-backed)
  • Ease: How easy is this to build? (1 = very hard, 10 = trivial)

MoSCoW Framework

### Must Have (Release fails without these)
- [Feature]: [Why it is essential]

### Should Have (Important but not critical)
- [Feature]: [Value and consequence of excluding]

### Could Have (Nice-to-have, include if time allows)
- [Feature]: [Value]

### Won't Have (Explicitly excluded from this release)
- [Feature]: [Why excluded, when it might return]

Kano Analysis

FeatureAbsentPresentCategory
[Name][User reaction][User reaction]Must-be / Performance / Delighter
  • Must-be: Expected. Users are unhappy without it, neutral with it.
  • Performance: More is better. Linear relationship with satisfaction.
  • Delighter: Unexpected. Users are neutral without it, thrilled with it.
  • Indifferent: Users do not care either way.

Step 4: Rank and Visualize

Sort by score and create a visual:

### Priority Ranking

| Rank | Feature | Score | Effort | Recommendation |
|------|---------|-------|--------|---------------|
| 1 | [Name] | [Score] | S | Build now |
| 2 | [Name] | [Score] | M | Build next |
| 3 | [Name] | [Score] | L | Plan for Q+1 |
| 4 | [Name] | [Score] | M | Deprioritize |
| 5 | [Name] | [Score] | S | Quick win -- slot in |

Value vs. Effort Matrix

        High Value
            |
   Do Next  |  Do First
            |
  ----------+----------
            |
   Don't Do |  Quick Wins
            |
        Low Value

   High Effort <---> Low Effort

Step 5: Validate and Document

Before finalizing:

  • Do the top priorities align with strategic goals?
  • Are quick wins included to maintain momentum?
  • Is there a mix of user-facing and infrastructure work?
  • Have you accounted for dependencies between features?
  • Would stakeholders find this ranking defensible?
## Feature Prioritization: [Context]
Date: [Date] | Framework: [RICE/ICE/MoSCoW/Kano]

### Prioritization Criteria
[What dimensions were used and why]

### Scored Feature List
[Full scoring table]

### Recommended Priority Order
[Ranked list with rationale for top 5]

### Trade-offs and Decisions
- [Feature X over Feature Y because...]
- [Feature Z deprioritized despite requests because...]

### Next Steps
- [What to build this sprint/quarter]
- [What to revisit next period]

Examples

Example 1: Quarterly Planning

User: "We have 15 feature requests. Help me pick the top 5 for next quarter." Response: Use RICE scoring for a data-driven approach. Score all 15 features. Rank by RICE score. Validate the top 5 against team capacity. Highlight any high-impact items that scored low due to effort and suggest phased approaches.

Example 2: Quick Triage

User: "Which of these 6 features should we build first?" Response: Use ICE for speed. Score each on a 1-10 scale for Impact, Confidence, and Ease. Rank and recommend. Flag any features where low confidence significantly affects the ranking.

Example 3: Release Scoping

User: "We need to cut scope for the launch. What stays and what goes?" Response: Use MoSCoW. Categorize each feature as Must/Should/Could/Won't. Verify that Must-haves fit within capacity. Move borderline Should-haves to Could if capacity is tight.

Best Practices

  1. No framework is objective. RICE and ICE scores feel quantitative but the inputs are estimates. Use frameworks to structure discussion, not to avoid judgment.
  2. Calibrate as a team. Score collaboratively. When two people score Impact as 1 and 3, the discussion about why is more valuable than the number.
  3. Revisit periodically. Priorities change as you learn. Re-score quarterly or when significant new information arrives.
  4. Do not let squeaky wheels win. Loud customers or stakeholders can distort prioritization. Use frameworks to counterbalance lobbying with data.
  5. Account for dependencies. A feature that unlocks three others has compounding value. Score the package, not just the individual feature.
  6. Include cost of delay. Some features become less valuable over time (competitive response) or more valuable (regulatory deadline). Factor timing into scoring.
  7. Separate prioritization from estimation. Prioritize first (what matters most), then estimate (how long will it take). Mixing the two leads to building easy things instead of important things.
  8. Document your reasoning. The ranking will be questioned. Record why each feature was placed where it was so you can have informed discussions rather than starting over.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.