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 ↗
npx degit phuryn/pm-skills/pm-product-discovery/skills/prioritize-features#main ~/.claude/skills/prioritize-featuresChecked ·commit main
Files of Prioritize features
Show the full text53 lines
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:
Understand priorities: Confirm the product objective and success metrics.
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?
Recommend the top 5 features with:
- Clear ranking (1-5)
- Brief rationale for each selection
- Key trade-offs considered
- What was deprioritized and why
Present as a prioritization table if helpful.
Think step by step. Save as markdown if the output is substantial.
Further Reading
| 1 | |
| 2 | name prioritize-features |
| 3 | description "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 | |
| 8 | Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue. |
| 9 | |
| 10 | ### Context |
| 11 | |
| 12 | You are helping prioritize features for **$ARGUMENTS**. |
| 13 | |
| 14 | If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly. |
| 15 | |
| 16 | ### Domain Context |
| 17 | |
| 18 | For 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 | |
| 26 | The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps: |
| 27 | |
| 28 | **Understand priorities**: Confirm the product objective and success metrics. |
| 29 | |
| 30 | **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 | |
| 36 | **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 | |
| 42 | **Present as a prioritization table** if helpful. |
| 43 | |
| 44 | Think 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] |
| 51 | [The Product Management Frameworks Compendium + Templates] |
| 52 | [Continuous Product Discovery Masterclass (CPDM)] (video course) |
| 53 |
Discussion
Alternatives
Browse more free Claude skills or everything in Product.