Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Product Feature Backlog Prioritizer

agent product skill risk: low

Product Feature Backlog Prioritizer

Evaluate and rank a backlog of feature ideas based on impact, effort, risk, and strategic alignment, then recommend the top 5 with rationales and trade-offs.

SKILL 1 file

SKILL.md
---
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)

INPUTS

$ARGUMENTS REQUIRED

product or project name/context

REQUIRED CONTEXT

  • product objective
  • desired outcomes / success metrics
  • list of feature ideas

OPTIONAL CONTEXT

  • spreadsheets
  • backlogs
  • opportunity assessments
  • customer data for Opportunity Score

ROLES & RULES

Role assignments

  • You are helping prioritize features for **$ARGUMENTS**.
  1. If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly.
  2. Think step by step.
  3. Save as markdown if the output is substantial.

EXPECTED OUTPUT

Format
markdown
Schema
table · Ranking, Rationale, Key trade-offs, Deprioritized items
Constraints
  • include clear ranking 1-5
  • provide brief rationale for each
  • note key trade-offs
  • explain what was deprioritized and why
  • use prioritization table if helpful

SUCCESS CRITERIA

  • Confirm the product objective and success metrics.
  • Evaluate each feature on Impact, Effort, Risk, and Strategic alignment.
  • Recommend exactly the top 5 features with ranking and rationale.
  • Present as a prioritization table if helpful.

FAILURE MODES

  • May skip confirming priorities with the user.
  • May fail to apply Opportunity Score or ICE/RICE when data is available.

CAVEATS

Dependencies
  • User-provided product objective, desired outcomes, and feature ideas
  • Optional uploaded files (spreadsheets, backlogs)
Missing context
  • Explicit output format requirements (e.g., markdown structure, table columns).
Ambiguities
  • Does not specify desired output length or level of detail for rationales and trade-offs.
  • 'If the user provides files... read and analyze them directly' leaves file handling implicit.

QUALITY

OVERALL
0.82
CLARITY
0.85
SPECIFICITY
0.80
REUSABILITY
0.90
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Add a required output schema or template (e.g., 'Always return a markdown table with columns: Rank, Feature, Impact, Effort, Risk, Alignment, Rationale').
  • Replace $ARGUMENTS with a clearer placeholder such as {{product_context}} and document expected substitution.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT