analyze-feature-requests

Categorize and prioritize customer feature requests by theme, impact, effort, and strategic alignment.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/stefanomartiradonna/claude-skills --skill analyze-feature-requests-stefanomartiradonna
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-feature-requests
Source: https://github.com/stefanomartiradonna/claude-skills/tree/main/pm-product-discovery-analyze-feature-requests
Command: npx skills add https://github.com/stefanomartiradonna/claude-skills --skill analyze-feature-requests-stefanomartiradonna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams receive scattered feature requests from customers and struggle to decide which ones deserve development effort. This Skill turns a raw list of requests into a prioritized analysis grounded in product goals, so decisions are based on impact, effort, risk, and strategic fit rather than the loudest customer voice. ## Core Features & Use Cases - Theme Grouping: Clusters related feature requests into named themes for clearer analysis. - Structured Prioritization: Scores the top 3 features on impact, effort, risk, and strategic alignment, with Opportunity Score (Importance x (1 - Satisfaction)) framing from Dan Olsen. - Assumption Testing: For each top feature, provides rationale, alternative solutions, high-risk assumptions, and minimal-effort tests to validate them. - Use Case: You have a spreadsheet of 40 customer feature requests and a quarterly goal to reduce churn. Provide the file and your goal, and receive a themed breakdown with a prioritized shortlist and validation plan. ## Quick Start Analyze these customer feature requests against our goal of improving onboarding completion and prioritize the top three.

Frequently Asked Questions about analyze-feature-requests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize customer feature requests?▼

Group requests into themes, then score the top candidates on impact, effort, risk, and strategic alignment with your product goal. This Skill walks through that process step by step and outputs a prioritized shortlist with rationale and validation tests.

How to analyze a feature request spreadsheet or CSV?▼

Provide the spreadsheet, CSV, or document directly along with your product objective. The requests are read, categorized into themes, and evaluated against your stated goals, with a summary table created when the data is structured.

What is the Opportunity Score for feature prioritization?▼

Opportunity Score, from Dan Olsen, equals Importance multiplied by (1 minus Satisfaction), normalized to 0-1. It prioritizes customer-reported problems rather than requested solutions, focusing effort on important needs that are currently underserved.

Should I build features exactly as customers request them?▼

No. Customers should describe problems, not design solutions. This Skill prioritizes underlying opportunities behind requests and suggests alternative solutions worth considering for each top feature.

When should I not use feature request prioritization?▼

Avoid it when you lack a clear product goal, since strategic alignment scoring depends on a stated objective. It is also less useful for urgent bug fixes or compliance work that bypasses normal prioritization.