Prioritization Advisor
Pick RICE, ICE, value/effort, or another model with context-specific implementation guidance so roadmap debates stop cycling frameworks.
Overview
Prioritization-advisor is an agent skill most often used in Validate (also Build, Grow) that guides you to the right prioritization framework for your stage and team context.
Install
npx skills add https://github.com/deanpeters/product-manager-skills --skill prioritization-advisorWhat is this skill?
- Adaptive questions on product stage, team size, and stakeholder dynamics
- Recommends one framework to avoid framework whiplash
- Flags mismatches (e.g. RICE for strategic bets, ICE when you need hard data)
- Interactive skill type with tailored implementation guidance
- Covers RICE, ICE, value/effort, and related scoring approaches
Adoption & trust: 1.4k installs on skills.sh; 5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have too many ideas and no agreement on whether RICE, ICE, or value/effort fits your stage, so prioritization meetings rerun the same framework debate.
Who is it for?
Solo founders or small PM-led teams choosing a prioritization model for roadmap planning, backlog grooming, or stakeholder reviews.
Skip if: Teams that already have an approved framework and scored backlog, or anyone who only needs automatic ticket ranking without a decision process.
When should I use this skill?
Deciding between RICE, ICE, value/effort, or another scoring approach based on stage, team context, and stakeholder needs.
What do I get? / Deliverables
You leave with one recommended framework and context-specific implementation guidance so the team can score and sequence work consistently.
- Recommended prioritization framework for your context
- Implementation guidance tailored to team and stakeholder dynamics
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Prioritization is the canonical validate moment: you are deciding what to build before committing engineering capacity. Scope subphase covers roadmap tradeoffs, framework choice, and stakeholder alignment before prototype or full build.
Where it fits
Choose between RICE and value/effort before locking the first three milestones for an MVP.
Reconcile a growing backlog with one scoring model after scope creep from early customers.
Decide how to weight retention fixes versus acquisition experiments when data maturity allows RICE-style inputs.
How it compares
Use instead of copying a generic RICE template when context (stage, data, strategic bets) should drive the model choice.
Common Questions / FAQ
Who is prioritization-advisor for?
Product managers, solo builders acting as their own PM, and small teams who need to align on how to prioritize before committing engineering time.
When should I use prioritization-advisor?
During validate scope when choosing what to build next, during build pm when re-scoring a roadmap, and during grow lifecycle when balancing maintenance vs new bets—especially when teams argue over RICE vs ICE vs value/effort.
Is prioritization-advisor safe to install?
It is advisory text guidance with no built-in shell or network access in the skill itself; review the Security Audits panel on this Prism page before installing any repo skill.
SKILL.md
READMESKILL.md - Prioritization Advisor
## Purpose Guide product managers in choosing the right prioritization framework by asking adaptive questions about product stage, team context, decision-making needs, and stakeholder dynamics. Use this to avoid "framework whiplash" (switching frameworks constantly) or applying the wrong framework (e.g., using RICE for strategic bets or ICE for data-driven decisions). Outputs a recommended framework with implementation guidance tailored to your context. This is not a scoring calculator—it's a decision guide that matches prioritization frameworks to your specific situation. ## Key Concepts ### The Prioritization Framework Landscape Common frameworks and when to use them: **Scoring frameworks:** - **RICE** (Reach, Impact, Confidence, Effort) — Data-driven, requires metrics - **ICE** (Impact, Confidence, Ease) — Lightweight, gut-check scoring - **Value vs. Effort** (2x2 matrix) — Quick wins vs. strategic bets - **Weighted Scoring** — Custom criteria with stakeholder input **Strategic frameworks:** - **Kano Model** — Classify features by customer delight (basic, performance, delight) - **Opportunity Scoring** — Rate importance vs. satisfaction gap - **Buy-a-Feature** — Customer budget allocation exercise - **Moscow** (Must, Should, Could, Won't) — Forcing function for hard choices **Contextual frameworks:** - **Cost of Delay** — Urgency-based (time-sensitive features) - **Impact Mapping** — Goal-driven (tie features to outcomes) - **Story Mapping** — User journey-based (narrative flow) ### Why This Works - **Context-aware:** Matches framework to product stage, team maturity, data availability - **Anti-dogmatic:** No single "best" framework—it depends on your situation - **Actionable:** Provides implementation steps, not just framework names ### Anti-Patterns (What This Is NOT) - **Not a universal ranking:** Frameworks aren't "better" or "worse"—they fit different contexts - **Not a replacement for strategy:** Frameworks execute strategy; they don't create it - **Not set-it-and-forget-it:** Reassess frameworks as your product matures ### When to Use This - Choosing a prioritization framework for the first time - Switching frameworks (current one isn't working) - Aligning stakeholders on prioritization process - Onboarding new PMs to team practices ### When NOT to Use This - When you already have a working framework (don't fix what isn't broken) - For one-off decisions (frameworks are for recurring prioritization) - As a substitute for strategic vision (frameworks can't tell you what to build) --- ### Facilitation Source of Truth Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill. It defines: - session heads-up + entry mode (Guided, Context dump, Best guess) - one-question turns with plain-language prompts - progress labels (for example, Context Qx/8 a