analyze-feature-requests

phuryn/pm-skills

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

What is analyze-feature-requests?

Systematically evaluate customer feature requests against product goals using structured prioritization criteria. Use this when triaging backlogs, reviewing customer feedback, or making go/no-go decisions on features.

Categorize requests into thematic groups
Assess strategic alignment with product objectives
Score opportunities using Importance × (1 − Satisfaction) framework
Prioritize top 3 features by impact, effort, risk, and alignment
Identify high-risk assumptions and minimal-effort validation tests
Generate structured prioritization output (markdown or table format)

How to install analyze-feature-requests

npx skills add https://github.com/phuryn/pm-skills --skill analyze-feature-requests

Claude Code

Cursor

Windsurf

Cline

How to use analyze-feature-requests

1.Provide your product goal and desired outcomes to guide prioritization
2.Supply feature requests as a list, spreadsheet, CSV, or document
3.Confirm the analysis framework (Opportunity Score = Importance × (1 − Satisfaction))
4.Review the categorized themes and strategic alignment assessment
5.Examine the top 3 prioritized features with rationale, alternatives, and risk assumptions
6.Use the suggested validation tests to de-risk assumptions before development

Use cases

Good for

Triaging a backlog of 50+ customer feature requests to identify top priorities
Evaluating quarterly roadmap candidates against stated product goals
Analyzing customer feedback from surveys or support tickets to find patterns
Deciding between competing feature themes when resources are limited
Testing market assumptions before committing engineering effort to a feature

Who it's for

Product managers
Product leads
Engineering managers making prioritization calls
Startup founders evaluating customer requests
Teams conducting product discovery

analyze-feature-requests FAQ

What if feature requests don't clearly map to product goals?

The skill will highlight misalignment and help you decide whether to adjust goals, reframe requests as underlying problems, or deprioritize them. Focus on opportunities (customer problems) rather than proposed solutions.

Can I use this for non-software products?

Yes. The framework applies to any product. Adjust 'effort' and 'risk' criteria to match your domain (e.g., manufacturing lead time, supply chain complexity).

How do I handle conflicting priorities from different customer segments?

The skill will surface these conflicts in the analysis. Use impact weighting to reflect your strategic focus (e.g., enterprise vs. SMB), then document trade-offs explicitly.

What's the difference between this and the prioritization-frameworks skill?

This skill applies prioritization frameworks (like Opportunity Score) to your specific feature requests. The prioritization-frameworks skill provides templates and deeper methodology reference.

Should I include technical debt or internal features?

Yes, if they block customer value or strategic goals. Categorize them separately and assess impact/effort/risk the same way.

Full instructions (SKILL.md)

Source of truth, from phuryn/pm-skills.

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:

Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization.
Categorize requests into themes: Group related requests together and name each theme.
Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals.
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
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