feature-prioritization_skill

This skill helps teams prioritize features using RICE, MoSCoW, Kano, and weighted scoring to inform roadmaps and resource decisions.

Shell

168

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill rsmdt/the-startup --skill feature-prioritization

SKILL.md11.7 KB

Overview

This skill provides practical implementations of RICE, MoSCoW, Kano, Cost of Delay, value-effort, and weighted scoring frameworks to prioritize product features and initiatives. It delivers scoring methodologies, estimation guidance, and a decision documentation template so teams make consistent, defensible trade-offs. Use it to convert opinions into repeatable, data-informed priorities and to create roadmap-ready rankings.

How this skill works

The skill applies one or more prioritization frameworks to candidate features by capturing measurable inputs (reach, impact, effort, confidence, weights, or delay costs) and computing scores or categories. It guides selection of an appropriate framework based on context, runs the math or categorization, and produces a Priority Decision Record that documents inputs, trade-offs, stakeholders, and review dates. Outputs include ranked lists, quadrant placements, Kano categories, CD3 urgency, and weighted score tables for direct comparison.

When to use it

Prioritizing a feature backlog for upcoming releases
Evaluating competing initiatives with limited capacity
Deciding build vs defer for features with stakeholder pressure
Creating or validating a product roadmap
Estimating economic impact of delaying a capability

Best practices

Choose the framework that fits the question: RICE for many similar items, MoSCoW for scope, Kano for user expectations
Use real data where possible (analytics, tickets, revenue) and capture confidence explicitly
Combine frameworks when useful (e.g., RICE + Cost of Delay or weighted scoring for strategic fit)
Document the decision, assumptions, and review date to enable follow-up
Time-box evaluations to avoid analysis paralysis and include key stakeholders

Example use cases

Rank 50 backlog items quickly using RICE to identify top candidates for the next quarter
Map a set of initiatives into the value vs effort matrix to find quick wins and time sinks
Run a Kano survey for new UX ideas to separate must-haves from delighters
Calculate CD3 for payment integrations to prioritize time-sensitive revenue opportunities
Build a weighted scoring model to align features with strategic objectives and budget

FAQ

Pick the framework that matches the decision. Use RICE for quantitative comparisons across many similar items, MoSCoW to define release scope, Kano to assess user satisfaction impact, and Cost of Delay for time-sensitive economic impact.

How do I handle uncertainty in estimates?

Capture confidence explicitly in your scoring (e.g., RICE confidence or a feasibility weight), run sensitivity checks, and label low-confidence items for discovery or smaller experiments before committing large effort.

What should the decision record include?

Include date, decision (prioritize/defer/reject), framework used, raw scores or categories, trade-offs considered, stakeholders and their positions, and a review date for deferred items.