Agent skill · Data & Analytics

define-prioritization-framework

Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.

product-on-purposegithub.com/product-on-purposeGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add product-on-purpose/pm-skills --skill define-prioritization-framework --agent claude-code

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

Facts
Files in the skill folder: 5
SKILL.md size: 13 KB
Bundled scripts: none
Version: 1.2.0
Declared author: product-on-purpose
Path: skills/define-prioritization-framework/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 518
Language: JavaScript

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

From the SKILL.md

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # Prioritization Framework You run all applicable prioritization frameworks against a candidate list of work items. Your job is to (a) filter frameworks by data availability and context, (b) score each item explicitly per applicable framework, (c) produce a comparison table showing where rankings agree and diverge, (d) synthesize an executive summary with recommendation, and (e) flag what could go wrong with the prioritization. ## Identity - Phase skill (define); Triple Diamond integration - Single-turn lifetime; produces one ranked artifact per invocation - Read-only tools (Read, Grep); no write outside the output artifact - Outputs a markdown document with per-framework scoring tables + comparison + recommendation ## Core principle **Multi-framework analysis surfaces what single-framework selection hides.** Where RICE and ICE agree, confidence rises. Where they disagree, the divergence reveals hidden assumptions worth examining - often the most valuable finding. Filter frameworks by applicability: RICE requires quantitative reach/impact/effort inputs; ICE works with coarse estimates; MoSCoW is for b

What's inside
Steps it walks through
  1. Identity
  2. Core principle
  3. When NOT to Use
  4. Inputs
  5. Framework applicability filter
  6. What you produce
  7. 1. Applicability filter summary (3-5 sentences)
  8. 2. Inputs summary
  9. 3. Per-framework scoring tables
  10. 4. Per-framework ranking output
  11. 5. Cross-framework comparison
  12. 6. Executive summary with recommendation
  13. 7. Sensitivity / what changes the ranking
  14. 8. Recommendations (sequencing)
Ships with 4 files
  • HISTORY.md
  • evals/trigger-fixtures.json
  • references/EXAMPLE.md
  • references/TEMPLATE.md
More from pm-skills
All skills →
About this skill
What does the define-prioritization-framework skill do?

Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.

How do I install it?

Run `npx skills add product-on-purpose/pm-skills --skill define-prioritization-framework --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 product-on-purpose/pm-skills, a repository with 518 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