/analyze-feature-requests
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.
One skill from pm-skills.
shell
$ npx -y skills add phuryn/pm-skills --skill analyze-feature-requests --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/analyze-feature-requests
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
Stats
Stars24,321
Forks2,503
LicenseMIT
SKILL.md
analyze-feature-requests.SKILL.md
--- 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: 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.