SkillAgentSearch skills...

prioritization-advisor

Choose a prioritization framework based on stage, team context, and stakeholder needs

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill prioritization-advisor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

Tags

Our assessment of prioritization-advisor

prioritization-advisor scores 90/100 on our quality scale, 25th of 60 Product Management skills we index (top 42%).

Its SKILL.md is 17 KB long, well organised into 43 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
17/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so prioritization-advisor is actively maintained.
  • Our last check on 2026-10-30 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

prioritization-advisor compared with similar skills

All 4 of these similar skills score higher than prioritization-advisor; compare them before choosing.

SkillScoreStarsUpdatedFormat
prioritization-advisor (this skill)by deanpeters907.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install prioritization-advisor?
Run npx skills add deanpeters/Product-Manager-Skills --skill prioritization-advisor. The install tabs above show the steps for each supported agent.
Which AI agents does prioritization-advisor work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is prioritization-advisor safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is prioritization-advisor still maintained?
The repository was last updated about 3 months ago, so prioritization-advisor is actively maintained.

name: prioritization-advisor argument-hint: "[decision context]" description: Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach. intent: >- 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. type: interactive best_for:

  • "Choosing the right prioritization framework for a team or stage"
  • "Deciding between RICE, ICE, value/effort, and similar models"
  • "Reducing debate about how to prioritize competing work" scenarios:
  • "Which prioritization framework should my startup use right now?"
  • "Help me choose between RICE and value/effort for roadmap planning"
  • "We keep arguing about prioritization. Recommend a framework." theme: strategy-positioning estimated_time: "15-25 min"

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.

Input

Works best with: What you're trying to prioritize and why now (sprint planning, roadmap, stakeholder fight). Also useful: Product stage, team size, data availability, and frameworks you've tried that failed.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. The advisor opens by asking about your product stage and the decision you need the framework to make.

Example invocation: Help me pick a framework: seed-stage B2B startup, 40-item backlog, zero usage data, loud enterprise prospect.

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 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 and Scoring Qx/5)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include Other (specify) when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

Application

This interactive skill asks up to 4 adaptive questions, offering 3-4 enumerated options at each step.


Question 1: Product Stage

Agent asks: "What stage is your product in?"

Offer 4 enumerated options:

  1. Pre-product/market fit — "Searching for PMF; experimenting rapidly; unclear what customers want" (High uncertainty, need speed)
  2. Early PMF, scaling — "Found initial PMF; growing fast; adding features to retain/expand" (Moderate uncertainty, balancing speed + quality)
  3. Mature product, optimization — "Established market; incremental improvements; competing on quality/features" (Low uncertainty, data-driven decisions)
  4. Multiple products/platform — "Portfolio of products; cross-product dependencies; complex stakeholder needs" (Coordination complexity)

Or describe your product stage (new idea, growth mode, established, etc.).

User response: [Selection or custom]


Question 2: Team Context

Agent asks: "What's your team and stakeholder environment like?"

Offer 4 enumerated options:

  1. Small team, limited resources — "3-5 engineers, 1 PM, need to focus ruthlessly" (Need simple, fast framework)
  2. Cross-functional team, aligned — "Product, design, engineering aligned; clear goals; good collaboration" (Can use data-driven frameworks)
  3. Multiple stakeholders, misaligned — "Execs, sales, customers all have opinions; need transparent process" (Need consensus-building framework)
  4. Large org, complex dependencies — "Multiple teams, shared roadmap, cross-team dependencies" (Need coordination framework)

Or describe your team/stakeholder context.

User response: [Selection or custom]


Question 3: Decision-Making Needs

Agent asks: "What's the primary challenge you're trying to solve with prioritization?"

Offer 4 enumerated options:

  1. Too many ideas, unclear which to pursue — "Backlog is 100+ items; need to narrow to top 10" (Need filtering framework)
  2. Stakeholders disagree on priorities — "Sales wants features, execs want strategic bets, engineering wants tech debt" (Need alignment framework)
  3. Lack of data-driven decisions — "Prioritizing by gut feel; want metrics-based process" (Need scoring framework)
  4. Hard tradeoffs between strategic bets vs. quick wins — "Balancing long-term vision vs. short-term customer needs" (Need value/effort framework)

Or describe your specific challenge.

User response: [Selection or custom]


Question 4: Data Availability

Agent asks: "How much data do you have to inform prioritization?"

Offer 3 enumerated options:

  1. Minimal data — "New product, no usage metrics, few customers to survey" (Gut-based frameworks)
  2. Some data — "Basic analytics, customer feedback, but no rigorous data collection" (Lightweight scoring frameworks)
  3. Rich data — "Usage metrics, A/B tests, customer surveys, clear success metrics" (Data-driven frameworks)

Or describe your data situation.

User response: [Selection or custom]


Output: Recommend Prioritization Framework

After collecting responses, the agent recommends a framework:

# Prioritization Framework Recommendation

**Based on your context:**
- **Product Stage:** [From Q1]
- **Team Context:** [From Q2]
- **Decision-Making Need:** [From Q3]
- **Data Availability:** [From Q4]

---

## Recommended Framework: [Framework Name]

**Why this framework fits:**
- [Rationale 1 based on Q1-Q4]
- [Rationale 2]
- [Rationale 3]

**When to use it:**
- [Context where this framework excels]

**When NOT to use it:**
- [Limitations or contexts where it fails]

---

## How to Implement

### Step 1: [First implementation step]
- [Detailed guidance]
- [Example: "Define scoring criteria: Reach, Impact, Confidence, Effort"]

### Step 2: [Second step]
- [Detailed guidance]
- [Example: "Score each feature on 1-10 scale"]

### Step 3: [Third step]
- [Detailed guidance]
- [Example: "Calculate RICE score: (Reach × Impact × Confidence) / Effort"]

### Step 4: [Fourth step]
- [Detailed guidance]
- [Example: "Rank by score; review top 10 with stakeholders"]

---

## Example Scoring Template

[Provide a concrete example of how to use the framework]

**Example (if RICE):**

| Feature | Reach (users/month) | Impact (1-3) | Confidence (%) | Effort (person-months) | RICE Score |
|---------|---------------------|--------------|----------------|------------------------|------------|
| Feature A | 10,000 | 3 (massive) | 80% | 2 | 12,000 |
| Feature B | 5,000 | 2 (high) | 70% | 1 | 7,000 |
| Feature C | 2,000 | 1 (medium) | 50% | 0.5 | 2,000 |

**Priority:** Feature A > Feature B > Feature C

---

## Alternative Framework (Second Choice)

**If the recommended framework doesn't fit, consider:** [Alternative framework name]

**Why this might work:**
- [Rationale]

**Tradeoffs:**
- [What you gain vs. what you lose]

---

## Common Pitfalls with This Framework

1. **[Pitfall 1]** — [Description and how to avoid]
2. **[Pitfall 2]** — [Description and how to avoid]
3. **[Pitfall 3]** — [Description and how to avoid]

---

## Reassess When

- Product stage changes (e.g., PMF → scaling)
- Team grows or reorganizes
- Stakeholder dynamics shift
- Current framework feels broken (e.g., too slow, ignoring important factors)

---

**Would you like implementation templates or examples for this framework?**

Examples

Example 1: Good Framework Match (Early PMF, RICE)

Q1 Response: "Early PMF, scaling — Found initial PMF; growing fast; adding features to retain/expand"

Q2 Response: "Cross-functional team, aligned — Product, design, engineering aligned; clear goals"

Q3 Response: "Lack of data-driven decisions — Prioritizing by gut feel; want metrics-based process"

Q4 Response: "Some data — Basic analytics, customer feedback, but no rigorous data collection"


Recommended Framework: RICE (Reach, Impact, Confidence, Effort)

Why this fits:

  • You have some data (analytics, customer feedback) to estimate Reach and Impact
  • Cross-functional team alignment means you can agree on scoring criteria
  • Transitioning from gut feel to data-driven = RICE provides structure without overwhelming complexity
  • Early PMF stage = need speed, but also need to prioritize high-impact features for retention/expansion

When to use it:

  • Quarterly or monthly roadmap planning
  • When backlog exceeds 20-30 items
  • When stakeholders debate priorities

When NOT to use it:

  • For strategic, multi-quarter bets (RICE favors incremental wins)
  • When you lack basic metrics (Reach requires usage data)
  • For single-feature decisions (overkill)

Implementation:

Step 1: Define Scoring Criteria

  • Reach: How many users will this feature affect per month/quarter?
  • *Impact:

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryProduct
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium