prioritize-features
This Claude Code skill evaluates and ranks feature backlogs to identify the top five priorities for development. Users should deploy it when making scope decisions, managing product roadmaps, or deciding which feature ideas to pursue next. The skill systematically assesses candidates across impact, effort, risk, and strategic alignment, optionally applying frameworks like Opportunity Score or ICE scoring to guide recommendations with clear trade-offs and rationale.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/prioritize-features && cp -r /tmp/prioritize-features/pm-product-discovery/skills/prioritize-features ~/.claude/skills/prioritize-featuresSKILL.md
## 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)
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.