Prioritize Features

by phuryn8607e3b07781No license26K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 weeks ago

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.

AI-generated overview

Ranks a product feature backlog by impact, effort, risk and strategic alignment, recommending a top 5.

What it does
This skill guides an agent through evaluating a backlog of feature ideas against impact, effort, risk and strategic alignment. It confirms the product objective and success metrics, scores each feature, and produces a ranked top 5 with rationale, trade-offs and deprioritized items. It may present results as a prioritization table and save substantial output as markdown.
When to use it
Use it when prioritizing a feature backlog, making scope decisions, or ranking product ideas. It fits product planning sessions where a shortlist of features must be chosen.
Requirements
No scripts or special tooling; it is instructions only. It can read user-provided files such as spreadsheets, backlogs or opportunity assessments if supplied.

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

Source and attribution

Source:phuryn/pm-skillsinpm-product-discovery/skills/prioritize-featuresat commit8607e3b

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal