analyze-feature-requests

Analyze and prioritize customer feature requests by theme, impact, effort, and risk.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill analyze-feature-requests-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-feature-requests
Source: https://github.com/moonzff/Codex_up/tree/main/skills/user-research/analyze-feature-requests
Command: npx skills add https://github.com/moonzff/Codex_up --skill analyze-feature-requests-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often receive scattered feature requests from customers and struggle to decide which ones deserve development resources. This Skill turns raw request lists into a structured, prioritized analysis grounded in product strategy. ## Core Features & Use Cases - Theme Categorization: Groups related feature requests into named themes for clearer backlog triage. - Prioritization Framework: Ranks the top 3 features using impact, effort, risk, and strategic alignment, with Opportunity Score (Importance x (1 - Satisfaction)) for customer-reported problems. - Assumption Testing: For each top feature, provides rationale, alternative solutions, high-risk assumptions, and minimal-effort validation tests. - Use Case: Paste a CSV export of customer feature requests along with your quarterly product goal, and receive a prioritized markdown report identifying the three highest-value opportunities and how to de-risk them. ## Quick Start Analyze the attached feature request spreadsheet against our goal of improving onboarding retention and recommend the top three priorities.

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 each theme on impact, effort, risk, and strategic alignment with your product goal. This Skill ranks the top three features and provides rationale, alternatives, and assumption tests for each.

What is the Opportunity Score framework for feature prioritization?▼

Opportunity Score, from Dan Olsen, equals Importance multiplied by (1 minus Satisfaction), normalized to a 0-10 scale. It prioritizes customer problems that are important but poorly served, rather than letting customers design solutions.

Can I analyze feature requests from a spreadsheet or CSV file?▼

Yes, attach spreadsheets, CSVs, or documents containing feature requests and they will be read and analyzed directly. Structured data may be summarized into a table before categorization and prioritization.

Should I prioritize features or customer problems?▼

Prioritize opportunities, meaning customer problems, not the features customers request. Customers are good at describing pain points but poor at designing solutions, so evaluate underlying needs against your product goals.

What inputs are required to run a feature request analysis?▼

You need a stated product objective and a list of feature requests, either pasted as text or attached as files. If a missing input materially changes the result, the Skill will ask before proceeding.