Purpose
Help PMs choose the right prioritization framework by asking adaptive questions about product stage, team context, decision-making needs, and data availability. Then guide implementation with templates and examples.
Key Concepts
Framework Landscape
| Framework |
Best For |
Data Needed |
| RICE |
Data-driven teams with metrics |
High — need reach, impact data |
| ICE |
Fast gut-check scoring |
Low — subjective scores |
| Value vs. Effort |
Quick visual prioritization |
Low — 2x2 matrix |
| Kano |
Feature delight classification |
Medium — customer surveys |
| MoSCoW |
Forcing hard scope decisions |
Low — stakeholder input |
| Cost of Delay |
Time-sensitive decisions |
Medium — urgency data |
| Weighted Scoring |
Complex multi-criteria decisions |
Medium — stakeholder alignment |
| Opportunity Scoring |
Customer-centric prioritization |
Medium — importance/satisfaction gaps |
Application
Question 1: Product Stage
Agent asks: "What stage is your product in?"
- Pre-PMF — Searching for product-market fit, experimenting rapidly
- Early PMF, scaling — Found fit, growing, adding features
- Mature product — Established, optimizing, incremental improvements
- Multi-product/platform — Portfolio, cross-product dependencies
Question 2: Team Context
Agent asks: "What's your team and stakeholder environment?"
- Small team, limited resources — Need simple, fast framework
- Cross-functional, aligned — Can use data-driven frameworks
- Multiple stakeholders, misaligned — Need consensus-building
- Large org, complex dependencies — Need coordination framework
Question 3: Decision Challenge
Agent asks: "What's the primary prioritization challenge?"
- Too many ideas — Need to narrow to top 10
- Stakeholder disagreement — Need transparent process
- Lack of data-driven decisions — Want metrics-based scoring
- Strategic vs. tactical tradeoffs — Balancing long vs. short term
Question 4: Data Availability
Agent asks: "How much data do you have?"
- Minimal — New product, few metrics
- Some — Basic analytics, some feedback
- Rich — Usage metrics, A/B tests, surveys
Output: Framework Recommendation + Implementation Guide
# Prioritization Framework Recommendation
**Context:** [Summary from Q1-Q4]
## Recommended: [Framework Name]
**Why it fits:** [Rationale tied to each answer]
## Implementation
### Step 1: [Setup]
[Detailed guidance]
### Step 2: [Scoring/Evaluation]
[Template with example]
### Step 3: [Review and Decide]
[How to use the output]
## Scoring Template
| Item | [Criteria 1] | [Criteria 2] | [Criteria 3] | Score |
|------|-------------|-------------|-------------|-------|
| [Feature A] | [#] | [#] | [#] | [Total] |
## Alternative: [Second choice framework]
Consider if [condition].
Quality Rubric
| Dimension |
0 |
1 |
2 |
| Context Fit |
Generic recommendation |
Matches 1-2 dimensions |
Matches all 4 context dimensions |
| Actionability |
Framework name only |
Steps listed |
Full template + scored example |
| Alternatives |
None |
Mentioned |
With switching criteria |
References
Related Skills
skills/planning/epic-hypothesis/SKILL.md — Items to prioritizeskills/planning/roadmap-planning/SKILL.md — Prioritization feeds the roadmapskills/planning/now-next-later-roadmap/SKILL.md — Output format
External Frameworks
- Sean Ellis, RICE; Intercom, Prioritization articles
Skill type: Interactive
Domain: Planning & Prioritization
1---2name: prioritization-advisor3description: Guide PMs in choosing the right prioritization framework — RICE, ICE, Kano, MoSCoW, Value vs Effort, Cost of Delay — by asking adaptive questions about product stage, team context, and data availability.4---56## Purpose78Help PMs choose the **right prioritization framework** by asking adaptive questions about product stage, team context, decision-making needs, and data availability. Then guide implementation with templates and examples.910---1112## Key Concepts1314### Framework Landscape1516| Framework | Best For | Data Needed |17|-----------|----------|------------|18| **RICE** | Data-driven teams with metrics | High — need reach, impact data |19| **ICE** | Fast gut-check scoring | Low — subjective scores |20| **Value vs. Effort** | Quick visual prioritization | Low — 2x2 matrix |21| **Kano** | Feature delight classification | Medium — customer surveys |22| **MoSCoW** | Forcing hard scope decisions | Low — stakeholder input |23| **Cost of Delay** | Time-sensitive decisions | Medium — urgency data |24| **Weighted Scoring** | Complex multi-criteria decisions | Medium — stakeholder alignment |25| **Opportunity Scoring** | Customer-centric prioritization | Medium — importance/satisfaction gaps |2627---2829## Application3031### Question 1: Product Stage3233**Agent asks:** "What stage is your product in?"34351. **Pre-PMF** — Searching for product-market fit, experimenting rapidly362. **Early PMF, scaling** — Found fit, growing, adding features373. **Mature product** — Established, optimizing, incremental improvements384. **Multi-product/platform** — Portfolio, cross-product dependencies3940### Question 2: Team Context4142**Agent asks:** "What's your team and stakeholder environment?"43441. **Small team, limited resources** — Need simple, fast framework452. **Cross-functional, aligned** — Can use data-driven frameworks463. **Multiple stakeholders, misaligned** — Need consensus-building474. **Large org, complex dependencies** — Need coordination framework4849### Question 3: Decision Challenge5051**Agent asks:** "What's the primary prioritization challenge?"52531. **Too many ideas** — Need to narrow to top 10542. **Stakeholder disagreement** — Need transparent process553. **Lack of data-driven decisions** — Want metrics-based scoring564. **Strategic vs. tactical tradeoffs** — Balancing long vs. short term5758### Question 4: Data Availability5960**Agent asks:** "How much data do you have?"61621. **Minimal** — New product, few metrics632. **Some** — Basic analytics, some feedback643. **Rich** — Usage metrics, A/B tests, surveys6566### Output: Framework Recommendation + Implementation Guide6768```markdown69# Prioritization Framework Recommendation7071**Context:** [Summary from Q1-Q4]7273## Recommended: [Framework Name]7475**Why it fits:** [Rationale tied to each answer]7677## Implementation7879### Step 1: [Setup]80[Detailed guidance]8182### Step 2: [Scoring/Evaluation]83[Template with example]8485### Step 3: [Review and Decide]86[How to use the output]8788## Scoring Template89| Item | [Criteria 1] | [Criteria 2] | [Criteria 3] | Score |90|------|-------------|-------------|-------------|-------|91| [Feature A] | [#] | [#] | [#] | [Total] |9293## Alternative: [Second choice framework]94Consider if [condition].95```9697---9899## Quality Rubric100101| Dimension | 0 | 1 | 2 |102|-----------|---|---|---|103| **Context Fit** | Generic recommendation | Matches 1-2 dimensions | Matches all 4 context dimensions |104| **Actionability** | Framework name only | Steps listed | Full template + scored example |105| **Alternatives** | None | Mentioned | With switching criteria |106107---108109## References110111### Related Skills112- `skills/planning/epic-hypothesis/SKILL.md` — Items to prioritize113- `skills/planning/roadmap-planning/SKILL.md` — Prioritization feeds the roadmap114- `skills/planning/now-next-later-roadmap/SKILL.md` — Output format115116### External Frameworks117- Sean Ellis, RICE; Intercom, *Prioritization* articles118119---120121**Skill type:** Interactive122**Domain:** Planning & Prioritization
nandanosql