Analyze Feature Requests
Turn a messy list of customer feature asks into themed, goal-aligned priorities with impact, effort, and risk so you can say no without guessing.
Overview
Analyze Feature Requests is an agent skill most often used in Build (also Validate scope, Operate iterate) that categorizes customer feature asks, scores them against product goals, and recommends a prioritized top three
Install
npx skills add https://github.com/phuryn/pm-skills --skill analyze-feature-requestsWhat is this skill?
- Groups requests into named themes before scoring individual features
- Uses Opportunity Score framing (importance × unsatisfied need) via prioritization-frameworks
- Scores top candidates on impact, effort, and risk against a confirmed product objective
- Explicit rule: prioritize problems and opportunities, not customer-designed solutions
- Accepts spreadsheets, CSVs, and docs as direct inputs for summary tables
- Opportunity Score = Importance × (1 − Satisfaction), normalized 0–1
- Top 3 features prioritized per run
Adoption & trust: 1k installs on skills.sh; 12.3k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a pile of customer feature requests and no repeatable way to align them with strategy, impact, effort, and risk.
Who is it for?
Solo founders triaging CSVs, support exports, or verbal lists of requests before committing engineering time.
Skip if: Teams that already have a signed PRD and approved sprint backlog with no new inbound requests to evaluate.
When should I use this skill?
Reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
What do I get? / Deliverables
You get themed request groups and a defensible top-three priority list grounded in your stated product objective—then you can slot winners into sprint planning or roadmap updates.
- Themed request groups
- Strategic alignment notes per theme
- Prioritized top-three feature recommendation with rationale
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Backlog triage and customer-request analysis are core product-management work while you are actively building and shaping the roadmap. The pm subphase is where solo builders prioritize what to build next against stated product goals and capacity.
Where it fits
Narrow MVP scope by ranking which customer asks actually match your validation hypothesis.
Theme fifty support tickets into clusters and pick three for the next sprint.
Re-score inbound requests after a launch when satisfaction and importance signals shift.
How it compares
Structured PM triage workflow, not a generic brainstorming or coding skill.
Common Questions / FAQ
Who is analyze-feature-requests for?
Indie builders and small-product owners who own the backlog and need agent-guided prioritization when customer asks pile up.
When should I use analyze-feature-requests?
During Build pm when triaging a backlog; during Validate scope when deciding what belongs in an MVP; during Operate iterate when re-ranking requests after shipping feedback.
Is analyze-feature-requests safe to install?
Review the Security Audits panel on this Prism page before installing; the skill reads user-provided files and does not prescribe external network calls by itself.
Workflow Chain
Requires first: prioritization frameworks
SKILL.md
READMESKILL.md - Analyze Feature Requests
## 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)