prioritize-features

phuryn/pm-skills

Rank feature backlogs by impact, effort, risk, and strategic alignment to identify top 5 priorities.

What is prioritize-features?

Evaluates and ranks feature ideas using frameworks like Opportunity Score, ICE, and RICE to help product teams make scope decisions. Use when you have a backlog of feature ideas and need to identify which ones deliver the most value relative to effort and risk.

Scores features against impact, effort, risk, and strategic alignment dimensions
Applies prioritization frameworks (Opportunity Score, ICE, RICE) based on available data
Generates ranked top-5 recommendations with clear rationale
Identifies key trade-offs and deprioritized features with reasoning
Produces prioritization tables for easy comparison and decision-making

How to install prioritize-features

npx skills add https://github.com/phuryn/pm-skills --skill prioritize-features

Prerequisites

Feature ideas or backlog items to evaluate
Product objective and success metrics (clarified during the process)
Optional: spreadsheets, backlogs, or opportunity assessments with supporting data

Claude Code

Cursor

Windsurf

Cline

How to use prioritize-features

1.Describe your product objective and desired outcomes
2.Provide your list of feature ideas (as text, spreadsheet, or file)
3.Confirm which prioritization framework fits your context (Opportunity Score for customer problems, ICE/RICE for initiatives)
4.Review the ranked top-5 recommendations with rationale and trade-offs
5.Use the prioritization table to guide your roadmap and scope decisions

Use cases

Good for

Prioritizing a product backlog when deciding which features to build next
Evaluating customer problem opportunities using importance and satisfaction data
Ranking product ideas for a startup or new product line
Making scope decisions when resources are constrained
Assessing strategic fit of feature requests against product vision

Who it's for

Product managers
Product owners
Startup founders
Engineering leads making feature decisions
Teams conducting product discovery

prioritize-features FAQ

What's the difference between Opportunity Score, ICE, and RICE?

Opportunity Score (Importance × (1 − Satisfaction)) is best for evaluating customer problems. ICE (Impact × Confidence × Ease) is a quick scoring method for initiatives. RICE adds Reach as a separate factor for larger teams. Choose based on your data availability and team size.

Do I need customer data to use this skill?

No. The skill works with or without customer data. With data, it applies Opportunity Score for richer insights. Without it, it uses effort, risk, and strategic alignment to rank features.

Can I use this for prioritizing bugs vs. features?

This skill is designed for feature prioritization. For mixed backlogs, you can apply the same framework but typically separate critical bugs (fix immediately) from feature work before prioritizing.

What if I disagree with the top-5 ranking?

The ranking is a recommendation based on the framework and data provided. Use it as a starting point for discussion. The skill will explain trade-offs so you can adjust based on context the framework may not capture.

Should I prioritize solutions or problems?

Prioritize problems (opportunities), not solutions. The Opportunity Score framework is specifically designed to identify high-importance, low-satisfaction problems worth solving.

Full instructions (SKILL.md)

Source of truth, from phuryn/pm-skills.

name: prioritize-features 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."

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.