Agent skill

feature-prioritisation

Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items. Use when asked to prioritise features, rank a backlog, decide what to build next, or evaluate tradeoffs between competing ideas. Produces a scored, ranked feature list with framework-specific tables, recommended build order, deprioritised items, and assumptions made.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorships scriptsMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill feature-prioritisation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 8 KB
Bundled scripts: yes
Path: skills/feature-prioritisation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Feature Prioritisation Skill Apply the right prioritisation framework to any backlog and produce a clear, defensible ranking with rationale — not just a sorted list. ## Required Inputs Ask the user for these if not provided: - **List of features or initiatives to prioritise** - **Goal or metric** being prioritised against (OKR, launch, sprint) - **Preferred framework** (or recommend based on context below) - **Team data**: reach estimates, effort estimates, velocity (for RICE) ## Framework Selection Guide Ask the user which framework they prefer, or recommend based on context: | Situation | Recommended Framework | |---|---| | Need a quick, data-driven score | RICE | | Stakeholder alignment meeting | MoSCoW | | Understanding customer delight vs expectations | Kano | | Early-stage startup, fast decisions | ICE | | Identifying underserved customer needs | Opportunity Scoring | | Strategic portfolio decisions | Value vs Effort Matrix | --- ## RICE Scoring **Formula:** (Reach × Impact × Confidence) ÷ Effort | Factor | Definition | Scale | |---|---|---| | Reach | Users impacted per quarter | Actual number | | Impact | Effect on goal per user | 0.25 / 0.5 / 1 / 2 / 3 | | Confidence | Ho

What's inside
Steps it walks through
  1. Required Inputs
  2. Framework Selection Guide
  3. RICE Scoring
  4. MoSCoW Method
  5. ICE Scoring (Startup/fast mode)
  6. Kano Model
  7. Programmatic Helper
  8. Output Format
  9. Feature Prioritisation — [Product/Team] — [Date]
  10. Guidelines
  11. Deeper Materials
  12. Scoring Rubric (0–40)
  13. Quality Checks
  14. Anti-Patterns
Ships with 4 files
  • references/framework-selection.md
  • references/worked-example.md
  • scripts/feature_prioritisation.py
  • templates/prioritisation-session.md
Commands it runs
RICE from JSON
python3 scripts/feature_prioritisation.py initiatives.json --framework rice
RICE from CSV
python3 scripts/feature_prioritisation.py initiatives.csv --framework rice --format csv
ICE from JSON
python3 scripts/feature_prioritisation.py features.json --framework ice
Pipe into it
printf '%s\n' '[{"name":"API refactor","impact":8,"confidence":80,"ease":5}]' \
More from pm-claude-skills
All skills →
About this skill
What does the feature-prioritisation skill do?

Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items. Use when asked to prioritise features, rank a backlog, decide what to build next, or evaluate tradeoffs between competing ideas. Produces a scored, ranked feature list with framework-specific tables, recommended build order, deprioritised items, and assumptions made.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill feature-prioritisation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going