Prioritize features skill

Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations.

by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗

Use now

Files of Prioritize features

phuryn/main1 file shown
SKILL.md
Show the full text53 lines
prioritize-features/SKILL.md53 lines · 2.4 KB

Prioritize Feature Backlog

Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.

Context

You are helping prioritize features for $ARGUMENTS.

If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.

Domain Context

For framework selection guidance, see the prioritization-frameworks skill. Key recommendations:

Opportunity Score (Dan Olsen, The Lean Product Playbook) is recommended for evaluating customer problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. High Importance + low Satisfaction = best opportunities. Prioritize problems (opportunities), not solutions.

ICE is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. RICE adds Reach as a separate factor for larger teams.

Instructions

The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:

  1. Understand priorities: Confirm the product objective and success metrics.

  2. Evaluate each feature against:

    • Impact: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available.
    • Effort: How much development, design, and coordination is required?
    • Risk: How much uncertainty exists? What assumptions need testing?
    • Strategic alignment: How well does it fit the product vision and current goals?
  3. Recommend the top 5 features with:

    • Clear ranking (1-5)
    • Brief rationale for each selection
    • Key trade-offs considered
    • What was deprioritized and why
  4. Present as a prioritization table if helpful.

Think step by step. Save as markdown if the output is substantial.


Further Reading
1---
2name: prioritize-features
3description: "Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations. Use when prioritizing a feature backlog, making scope decisions, or ranking product ideas."
4---
5 
6## Prioritize Feature Backlog
7 
8Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue.
9 
10### Context
11 
12You are helping prioritize features for **$ARGUMENTS**.
13 
14If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.
15 
16### Domain Context
17 
18For framework selection guidance, see the `prioritization-frameworks` skill. Key recommendations:
19 
20**Opportunity Score** (Dan Olsen, *The Lean Product Playbook*) is recommended for evaluating customer problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. High Importance + low Satisfaction = best opportunities. Prioritize **problems (opportunities)**, not solutions.
21 
22**ICE** is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. **RICE** adds Reach as a separate factor for larger teams.
23 
24### Instructions
25 
26The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps:
27 
281. **Understand priorities**: Confirm the product objective and success metrics.
29 
302. **Evaluate each feature** against:
31 - **Impact**: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available.
32 - **Effort**: How much development, design, and coordination is required?
33 - **Risk**: How much uncertainty exists? What assumptions need testing?
34 - **Strategic alignment**: How well does it fit the product vision and current goals?
35 
363. **Recommend the top 5 features** with:
37 - Clear ranking (1-5)
38 - Brief rationale for each selection
39 - Key trade-offs considered
40 - What was deprioritized and why
41 
424. **Present as a prioritization table** if helpful.
43 
44Think step by step. Save as markdown if the output is substantial.
45 
46---
47 
48### Further Reading
49 
50- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
51- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
52- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
53 

Discussion

Alternatives