/prioritize-features
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.
Claude Code
$ npx -y skills add phuryn/pm-skills --skill prioritize-features --agent claude-code
Codex
$ npx skills add phuryn/pm-skills --skill prioritize-features -a codex -y
Cursor
$ npx skills add phuryn/pm-skills --skill prioritize-features -a cursor -y
Gemini CLI
$ npx skills add phuryn/pm-skills --skill prioritize-features -a gemini-cli -y
GitHub Copilot
$ npx skills add phuryn/pm-skills --skill prioritize-features -a github-copilot -y
OpenCode
$ npx skills add phuryn/pm-skills --skill prioritize-features -a opencode -y
Windsurf
$ npx skills add phuryn/pm-skills --skill prioritize-features -a windsurf -y
SKILL.md
prioritize-features.SKILL.mdname: 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:
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
- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
Read more
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:
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
- [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers)
- [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium)
- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
72 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Other skills on pm-skills.
More skills from other plugins.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
distilly
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…
openwork-connect
Search and use the skills, MCP connections, and connected services available through the user's OpenWork organization.
Questions about prioritize-features.
- Which coding agents can use prioritize-features?
- prioritize-features installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

