Prioritize Features

A structured approach to ranking feature backlogs when you need to get out of endless debate and ship something. It walks you through evaluating ideas against impact, effort, risk, and strategic alignment, then surfaces the top 5 with clear rationale. Points you toward Opportunity Score for customer problems and ICE for quick initiative scoring, which is solid advice. The real value is forcing you to articulate why you're deprioritizing things, not just what made the cut. Works directly with spreadsheets and backlog files if you have them. Honestly most useful when you've got 20+ ideas floating around and need a systematic way to defend your roadmap choices to stakeholders.

skills.sh installs: 3K
GitHub stars: 27.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add phuryn/pm-skills --skill prioritize-features --agent claude-code

Installs into .claude/skills of the current project.

Files

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.