prioritization-advisor

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
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