define-prioritization-framework

Scores candidate features across RICE, ICE, MoSCoW, Weighted Scoring, and Kano frameworks with cross-framework comparison.

640|81|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill define-prioritization-framework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: define-prioritization-framework
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-prioritization-framework
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill define-prioritization-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product teams often rank backlogs with a single framework or gut feel, hiding the assumptions that drive the ranking. This Skill runs every applicable prioritization framework against a candidate list, surfaces where rankings agree and diverge, and refuses to fabricate scores when input data is missing.

Core Features & Use Cases

  • Multi-framework scoring: Runs RICE, ICE, MoSCoW, Weighted Scoring, and Kano, filtered by data availability, with per-framework scoring tables and rankings.
  • Cross-framework divergence analysis: Produces a comparison table showing rank positions per item and explains each divergent item by naming the driving dimension.
  • Honest refusal protocols: Declines to fabricate scores, offers an estimation scaffold when inputs are missing, and gates Kano on customer research with surveyed and inferred evidence tiers.
  • Use Case: A PM with six Q3 roadmap candidates and rough reach, impact, and effort estimates gets RICE, ICE, and MoSCoW tables, a divergence analysis revealing that RICE under-weights a revenue-concentrated enterprise feature, and an executive recommendation on what to fund and defer.

Quick Start

Ask the AI to run the applicable prioritization frameworks against your list of candidate features and show where the rankings agree and diverge.

Frequently Asked Questions about define-prioritization-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize a product backlog with RICE and ICE?

Provide a list of candidate items with a decision context, and the Skill scores each item under RICE and ICE plus any other applicable framework. It then compares rankings across frameworks and explains where and why they diverge.

What is the difference between RICE, ICE, MoSCoW, and Kano prioritization?

RICE uses quantitative reach, impact, confidence, and effort; ICE uses coarse 1-10 judgment scores; MoSCoW buckets items by commitment level; Kano categorizes features by customer satisfaction impact. The Skill runs all frameworks that pass its data-availability filter rather than forcing one.

Can I run Kano analysis without customer survey data?

Kano is excluded when no customer research exists at all. With summarized signals like interview themes or support patterns, it runs at the inferred tier and labels categories as hypotheses; formal Kano question pairs earn the surveyed tier.

What happens if I do not have reach or effort estimates for RICE?

The Skill refuses to fabricate RICE scores and offers three options: provide rough numbers, receive an estimation scaffold worksheet for building the estimates, or fall back to ICE, which works with coarse judgment inputs.

When should I not use a multi-framework prioritization scoring approach?

Skip it when you have fewer than three candidate items, no defined candidate list yet, or a raw unstructured situation. It ranks an existing list; it does not discover opportunities, size markets, or produce a general action plan.