prioritization-frameworks
/prioritization-frameworks
Dobiera metodę priorytetyzacji i układa backlog: RICE, ICE, opportunity, MoSCoW i punktację ważoną, gdy porównuje się funkcje lub inicjatywy.
- Autor
- borghei ↗
- Repozytorium
- Claude-Skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 08.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 9
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 08.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/prioritization_scorer.py
Co robi i kiedy
Dobiera metodę priorytetyzacji i układa backlog: RICE, ICE, opportunity, MoSCoW i punktację ważoną, gdy porównuje się funkcje lub inicjatywy.
Oryginalny opis (EN)
Pick a prioritization method and rank a backlog: RICE, ICE, opportunity, MoSCoW and weighted scoring, plus four reference-only methods. Use when ranking features, problems or initiatives against each other.
Jak działa
- Overview
- Core Capabilities
- When to Use
- Clarify First
- Workflow
- Anti-Patterns
- References
- Files
- Scope & Limitations
- Integration Points
Podgląd SKILL.md
---
name: prioritization-frameworks
description: >
Pick a prioritization method and rank a backlog: RICE, ICE, opportunity,
MoSCoW and weighted scoring, plus four reference-only methods. Use when
ranking features, problems or initiatives against each other.
license: MIT + Commons Clause
metadata:
version: 1.0.2
author: borghei
category: project-management
domain: pm-execution
updated: 2026-11-08
python-tools: prioritization_scorer.py
tech-stack: rice, ice, kano, moscow, eisenhower, opportunity-score, prioritization
tags:
- prioritization
- rice
- ice
- moscow
- kano
---
# Prioritization Framework Expert
## Overview
Nine prioritization frameworks and when to use each. Five are scored by the tool (RICE, ICE, Opportunity Score, MoSCoW, Weighted Decision Matrix); four are reference-only and applied by hand (Eisenhower, Impact vs Effort, Risk vs Reward, Kano). The core principle: prioritize problems (opportunities), not features. Features are solutions to problems. If you prioritize features directly, you skip the step of understanding whether the problem is worth solving.
## Core Capabilities
- **9 frameworks** — RICE, ICE, Opportunity Score, Eisenhower, Impact vs Effort, Risk vs Reward, Kano, Weighted Decision Matrix, MoSCoW (full definitions, formulas, and worked examples in `references/frameworks-catalog.md`).
- **Framework selection** — a decision tree maps the thing you are prioritizing (problems, features, personal tasks, high-uncertainty bets) to the right method.
- **Automated scoring** — `prioritization_scorer.py` ranks items for RICE, ICE, Opportunity, MoSCoW, and Weighted Decision Matrix.
- **Two-step discipline** — prioritize problems first (Opportunity Score), then prioritize solutions (RICE/ICE).
## When to Use
- **Backlog Grooming** -- Too many items, need to rank them objectively.
- **Quarterly Planning** -- Deciding which initiatives to invest in.
- **Stakeholder Alignment** -- Need a structured way to resolve competing priorities.
- **Feature Triage** -- Quick sorting of a long list into actionable categories.
## Clarify First
Before scoring, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
- **What you're ranking:** problems/opportunities vs features vs personal tasks (the decision tree picks the framework from this).
- **Framework:** rice / ice / opportunity / moscow / weighted (each requires different score fields and emits different rankings).
- **Quality of the estimates:** measured data vs guesses for reach/impact (guesses make RICE/ICE precision misleading; switch to a coarser method).
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
## Workflow
1. **Decide what you are ranking.** Problems first (Opportunity Score), then solutions to the chosen problems (RICE or ICE). Personal tasks: Eisenhower. Uncertain bets: Risk vs Reward. Decision tree: `references/frameworks-catalog.md`.
2. **Gather estimates with their sources.** Reach from data, Effort from engineering, Confidence capped at 50% without a written source.
3. **Score:**
```bash
python3 project-management/execution/prioritization-frameworks/scripts/prioritization_scorer.py \
--input project-management/execution/prioritization-frameworks/assets/sample_rice_items.json --framework rice
# --demo --framework ice|opportunity|moscow|weighted shows each input shape; --format json for pipelines
```
4. **Verify** [RECOMMENDED] before publishing: spot-check one score by hand (the report prints each formula), check no more than 30% of items share the top Impact value, and read the top five as a group: does the order match the strategy? If not, find which estimate is wrong rather than overriding the rank.
Input schemas per framework: `references/tool-and-troubleshooting.md`. Missing fields fall back to defaults (for example, MoSCoW items without a `category` are "Could Have"), so check the report for items that all landed in one bucket.
**Exit codes:** 0 ranked; 2 missing file, invalid JSON, wrong shape, or items that do not fit the chosen framework.
## Anti-Patterns
### Every item scores massive impact
**Mistake:** Most of the backlog gets Impact = 3 on the RICE scale.
**Why it happens:** Each item has a champion, and nobody wants theirs marked minor.
**Instead:** RICE ranks items against each other, so uniform impact ranks nothing. If more than 30% of items score 3, recalibrate: only items with behavioural or revenue evidence keep it.
### Confidence padded to reach the cut line
**Mistake:** A favoured item's Confidence moves from 50% to 80% with no new evidence.
**Why it happens:** The ranking was decided first, and the score is adjusted to match it.
**Instead:** Add a Confidence Source column. An item with no written source is capped at 50%.
### Effort scored without engineering
**Mistake:** The PM sizes Effort alone, as small, medium or large.
**Why it happens:** It is quicker than booking engineers, and backend, security and migration work is hard to see from the product side.
**Instead:** Effort is the denominator, so a wrong estimate flips the ranking. Don't publish a score until an engineer has signed off on its Effort.
Eight more in `references/red-flags.md`; framework-specific mistakes in `references/prioritization-guide.md`.
## References
Load the reference that matches the task — keep this file lean and pull detail on demand:
- **[references/frameworks-catalog.md](references/frameworks-catalog.md)** — full definitions, formulas, strengths/weaknesses, and worked examples for all 9 frameworks, the framework decision tree, and the "prioritize problems, not features" principle. Read when choosing or applying a specific framework.
- **[references/prioritization-guide.md](references/prioritization-guide.md)** — detailed formulas, decision tree, and facilitation tips. Read when facilitating a scoring session with a group.
- **[references/red-flags.md](references/red-flags.md)** — anti-patterns and warning signs in prioritization practice. Read when a process feels off or results are being gamed.
- **[references/tool-and-troubleshooting.md](references/tool-and-troubleshooting.md)** — `prioritization_scorer.py` flags, per-framework input JSON schemas, troubleshooting table, and success criteria. Read when running the tool or diagnosing scoring problems.
## Files
| File | Purpose |
|---|---|
| `scripts/prioritization_scorer.py` | Scores and ranks for the five scored frameworks |
| `assets/sample_rice_items.json` | Five RICE items (Advanced search scores 2666.67) |
| `assets/prioritization_matrix_template.md` | Manual scoring templates for every framework |
| `examples/rice-vs-ice-q3-backlog.md` | Same backlog ranked two ways |
## Scope & Limitations
**In Scope:**
- 9 prioritization frameworks explained
- Scored and ranked by the tool (5): RICE, ICE, Opportunity Score, MoSCoW, Weighted Decision Matrix
- Reference-only, applied by hand (4): Eisenhower, Impact vs. Effort, Risk vs. Reward, Kano
- Framework selection guidance via Decision Tree
- Demo data for each framework to illustrate input/output formats
**Out of Scope:**
- Real-time Jira/Linear backlog integration (manual JSON input required)
- Cost-of-delay or WSJF calculations (see `senior-pm/` skill for SAFe portfolio prioritization)
- User research to gather importance/satisfaction data for Opportunity Score (see `product-team/` skills)
- Strategic portfolio allocation decisions (see `senior-pm/` skill)
**Important Caveats:**
- No framework produces a "correct" answer. Prioritization frameworks are decision-support tools that structure conversation, not algorithms that replace judgment.
- RICE and ICE are best for data-rich environments. If your reach and impact estimates are pure guesses, the precision of the formula is misleading.
- The most successful teams combine frameworks: start with Opportunity Score to identify the right problems, then use RICE to rank solutions.
- For teams with 50+ people or multiple stakeholder groups, use WSJF or Weighted Decision Matrix with agreed criteria to ensure buy-in.
## Integration Points
| Integration | Direction | Description |
|------------|-----------|-------------|
| `execution/outcome-roadmap/` | Feeds into | Prioritized items inform Now/Next/Later horizon placement |
| `execution/create-prd/` | Feeds into | Top-priority items become PRD candidates with P0/P1/P2 feature labels |
| `execution/brainstorm-okrs/` | Complements | Prioritized initiatives inform which OKR theme to focus on this quarter |
| `discovery/identify-assumptions/` | Receives from | Assumption risk scores inform item confidence ratings in RICE/ICE |
| `scrum-master/` | Feeds into | Prioritized backlog items feed sprint planning commitment decisions |
| `senior-pm/` | Receives from | Portfolio-level WSJF or strategic priorities constrain team-level prioritization |
Pliki w paczce (9)
- SKILL.md 9 KB
- assets/prioritization_matrix_template.md 4 KB
- assets/sample_rice_items.json 1 KB
- examples/rice-vs-ice-q3-backlog.md 10 KB
- references/frameworks-catalog.md 7 KB
- references/prioritization-guide.md 7 KB
- references/red-flags.md 11 KB
- references/tool-and-troubleshooting.md 4 KB
- scripts/prioritization_scorer.py 16 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · borghei/Claude-Skills | 100 | MIT |
| stefanoskarakasis/product-marketing-skills | 100 | MIT |
| phuryn/pm-skills | 95 | MIT |
| shrwnsan/vibekit-claude-plugins | 90 | Apache-2.0 |
| Amey-Thakur/AI-SKILLS | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 86da280677c0 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100prioritization
Szereguje funkcje, inicjatywy i problemy klientów metodami RICE, ICE, punktacją ważoną lub Opportunity Score oraz wskazuje linię cięcia. - 100prioritization
Wybiera metodę priorytetyzacji (RICE, ICE, MoSCoW, wpływ do wysiłku), ocenia pozycje i ustala linię odcięcia, gdy zadań jest więcej niż możliwości. - 100prioritization
Stosuje frameworki priorytetyzacji RICE, WSJF, ICE, MoSCoW i punktowanie kosztu alternatywnego do rankingu backlogu, porównywania inicjatyw i uzasadniania decyzji roadmapy. - 100score-backlog
Ocenia i szereguje pozycje backlogu metodami RICE, ICE lub własną ważoną punktacją przy priorytetyzacji backlogu i funkcji. - 100prioritization
Stosuje frameworki RICE, MoSCoW, ICE i wpływ-wysiłek do uszeregowania opcji i decyzji, nad czym pracować dalej, przy priorytetyzacji backlogu i cięciu zakresu. - 100product-strategy
Pomaga w wizji produktu, roadmapie i priorytetyzacji funkcji metodami RICE, ICE i MoSCoW oraz w OKR-ach produktowych.