Agent skill · product strategy · borghei
prioritization-frameworks
Comprehensive prioritization framework expert covering 9 methods with scoring tools and decision guidance for product managers.
Why this skill is useful
Adds an automated scoring script for multiple prioritization frameworks that enhances decision-making for product managers.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Prioritization Framework Expert Overview A comprehensive reference to 9 prioritization frameworks with automated scoring, ranking, and guidance on which framework to use in which situation. 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 — prioritizationscorer.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, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] 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) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/prioritization-frameworks