Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Feature Request Theme Analyzer and Prioritizer

product manager product skill risk: low

Feature Request Theme Analyzer and Prioritizer

Categorizes customer feature requests into themes, assesses strategic alignment with product goals, and prioritizes the top three features using impact, effort, risk, and Opportuni…

SKILL 1 file

SKILL.md
---
name: analyze-feature-requests
description: "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."
---
## Analyze Feature Requests

Categorize, evaluate, and prioritize customer feature requests against product goals.

### Context

You are analyzing feature requests for **$ARGUMENTS**.

If the user provides files (spreadsheets, CSVs, or documents with feature requests), read and analyze them directly. If data is in a structured format, consider creating a summary table.

### Domain Context

Never allow customers to design solutions. Prioritize **opportunities (problems)**, not features. Use **Opportunity Score** (Dan Olsen) to evaluate customer-reported problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. See the `prioritization-frameworks` skill for full details and templates.

### Instructions

The user will describe their product goal and provide feature requests. Work through these steps:

1. **Understand the goal**: Confirm the product objective and desired outcomes that will guide prioritization.

2. **Categorize requests into themes**: Group related requests together and name each theme.

3. **Assess strategic alignment**: For each theme, evaluate how well it aligns with the stated goals.

4. **Prioritize the top 3 features** based on:
   - **Impact**: Customer value and number of users affected
   - **Effort**: Development and design resources required
   - **Risk**: Technical and market uncertainty
   - **Strategic alignment**: Fit with product vision and goals

5. **For each top feature**, provide:
   - Rationale (customer needs, strategic alignment)
   - Alternative solutions worth considering
   - High-risk assumptions
   - How to test those assumptions with minimal effort

Think step by step. Save as markdown or create a structured output document.

---

### 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)
- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)

INPUTS

$ARGUMENTS REQUIRED

product or project name being analyzed

e.g. Acme Analytics Dashboard

REQUIRED CONTEXT

  • product goal
  • list of feature requests

OPTIONAL CONTEXT

  • files containing feature requests (spreadsheets, CSVs, documents)

TOOLS REQUIRED

  • file_search

ROLES & RULES

Role assignments

  • You are analyzing feature requests for **$ARGUMENTS**.
  1. Never allow customers to design solutions.
  2. Prioritize opportunities (problems), not features.
  3. Use Opportunity Score to evaluate customer-reported problems.

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Understand the goal, Categorize requests into themes, Assess strategic alignment, Prioritize the top 3 features, Rationale, alternatives, assumptions, tests for each top feature
Constraints
  • include themes with strategic alignment
  • prioritize top 3 features with rationale, alternatives, risks, and test ideas
  • use Opportunity Score where applicable

SUCCESS CRITERIA

  • Confirm the product objective
  • Group requests into named themes
  • Evaluate strategic alignment per theme
  • Prioritize top 3 features using impact, effort, risk, alignment
  • Provide rationale, alternatives, risks, and tests for each top feature

FAILURE MODES

  • May focus on features instead of underlying problems
  • May skip Opportunity Score calculation

CAVEATS

Dependencies
  • Requires product goal description from user
  • Requires list of feature requests (possibly in files)
Ambiguities
  • 'top 3 features' is ambiguous as to whether it means individual requests or themes
  • Output format is not specified beyond 'markdown or structured output document'

QUALITY

OVERALL
0.82
CLARITY
0.85
SPECIFICITY
0.75
REUSABILITY
0.90
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Add explicit output template or schema (e.g., required sections and table formats) to the Instructions
  • Clarify whether prioritization applies to themes or individual requests in step 4

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 PRODUCT MANAGER