Analyze feature requests skill
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk.
by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗
npx degit phuryn/pm-skills/pm-product-discovery/skills/analyze-feature-requests#main ~/.claude/skills/analyze-feature-requestsChecked ·commit main
Files of Analyze feature requests
Show the full text50 lines
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
Think step by step. Save as markdown or create a structured output document.
Further Reading
| 1 | |
| 2 | name analyze-feature-requests |
| 3 | 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." |
| 4 | |
| 5 | |
| 6 | ## Analyze Feature Requests |
| 7 | |
| 8 | Categorize, evaluate, and prioritize customer feature requests against product goals. |
| 9 | |
| 10 | ### Context |
| 11 | |
| 12 | You are analyzing feature requests for **$ARGUMENTS**. |
| 13 | |
| 14 | 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. |
| 15 | |
| 16 | ### Domain Context |
| 17 | |
| 18 | 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. |
| 19 | |
| 20 | ### Instructions |
| 21 | |
| 22 | The user will describe their product goal and provide feature requests. Work through these steps: |
| 23 | |
| 24 | **Understand the goal**: Confirm the product objective and desired outcomes that will guide prioritization. |
| 25 | |
| 26 | **Categorize requests into themes**: Group related requests together and name each theme. |
| 27 | |
| 28 | **Assess strategic alignment**: For each theme, evaluate how well it aligns with the stated goals. |
| 29 | |
| 30 | **Prioritize the top 3 features** based on: |
| 31 | **Impact**: Customer value and number of users affected |
| 32 | **Effort**: Development and design resources required |
| 33 | **Risk**: Technical and market uncertainty |
| 34 | **Strategic alignment**: Fit with product vision and goals |
| 35 | |
| 36 | **For each top feature**, provide: |
| 37 | Rationale (customer needs, strategic alignment) |
| 38 | Alternative solutions worth considering |
| 39 | High-risk assumptions |
| 40 | How to test those assumptions with minimal effort |
| 41 | |
| 42 | Think step by step. Save as markdown or create a structured output document. |
| 43 | |
| 44 | |
| 45 | |
| 46 | ### Further Reading |
| 47 | |
| 48 | [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory] |
| 49 | [Continuous Product Discovery Masterclass (CPDM)] (video course) |
| 50 |
Discussion
Alternatives
Academy guideStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
Advocacy program designerUse when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规Act as a product managerGuides the AI to act as a product manager, assisting in writing product requirement documents and addressing product-related queries.
Incremental implementationDelivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step.Browse more free Claude skills or everything in Product.