Productivity
Skill
/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.
Claude Code
$ npx -y skills add phuryn/pm-skills --skill analyze-feature-requests --agent claude-code
Codex
$ npx skills add phuryn/pm-skills --skill analyze-feature-requests -a codex -y
Cursor
$ npx skills add phuryn/pm-skills --skill analyze-feature-requests -a cursor -y
Gemini CLI
$ npx skills add phuryn/pm-skills --skill analyze-feature-requests -a gemini-cli -y
GitHub Copilot
$ npx skills add phuryn/pm-skills --skill analyze-feature-requests -a github-copilot -y
OpenCode
$ npx skills add phuryn/pm-skills --skill analyze-feature-requests -a opencode -y
Windsurf
$ npx skills add phuryn/pm-skills --skill analyze-feature-requests -a windsurf -y
SKILL.md
analyze-feature-requests.SKILL.mdname: 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.
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)
Read more
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.
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)
Stats
27,892
Stars
2,883
Forks
Active
Maintenance
MIT
License
Last commit
Created
Ships withpm-skills
72 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
28k72 skills
Stars on GitHub
Momentum
- stars in total
- 28.0k
Other skills on pm-skills.
More skills from other plugins.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
@ayghriInstall Skill
distilly
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…
@titanwingsInstall Skillopenwork-connect
Search and use the skills, MCP connections, and connected services available through the user's OpenWork organization.
@different-aiInstall SkillQuestions about analyze-feature-requests.
- Which coding agents can use analyze-feature-requests?
- analyze-feature-requests installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.