analyze-feature-requests — Claude Code skill
This skill sorts feature requests into themes and ranks them by impact, effort, risk, and fit with product goals.
npx skills add phuryn/pm-skills --skill analyze-feature-requests -a claude-codeWhat analyze-feature-requests does
The skill takes a product goal and a set of feature requests. It groups related requests into named themes, checks their strategic fit, and selects the top 3 features using impact, effort, risk, and alignment with the product vision.
For every selected feature, it gives the reasoning, alternative solutions, high-risk assumptions, and low-effort ways to test those assumptions. It can read spreadsheets, CSV files, and documents directly. Structured material can be turned into a summary table.
The assessment centres on customer problems rather than customer-designed solutions. That distinction matters: the skill uses Opportunity Score, calculated as Importance × (1 − Satisfaction) and normalized to 0–1.
What it helps with
- group related feature requests into themes
- compare request themes with product goals
- rank the top 3 features
- surface high-risk assumptions
- plan low-effort assumption tests
Example prompts for the agent
- Use the analyze-feature-requests skill for this product goal and these customer requests.
- Run analyze-feature-requests on this CSV and rank the themes by impact, effort, and risk.
- Apply analyze-feature-requests to this backlog and suggest tests for the riskiest assumptions.
How to install analyze-feature-requests
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill analyze-feature-requests -a claude-code2Manually: put the files in place
~/.claude/skills/analyze-feature-requests/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/analyze-feature-requests/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill analyze-feature-requests -a codex2Manually: put the files in place
.agents/skills/analyze-feature-requests/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill analyze-feature-requests -a cursor2Manually: put the files in place
.cursor/skills/analyze-feature-requests/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install phuryn/pm-skills analyze-feature-requests2Manually: put the files in place
.github/skills/analyze-feature-requests/SKILL.md1Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill analyze-feature-requests -a gemini-cli2Platform CLI
gemini skills install https://github.com/phuryn/pm-skills --path pm-product-discovery/skills/analyze-feature-requestsManually: put the files in place
.devin/skills/analyze-feature-requests/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add phuryn/pm-skills --skill analyze-feature-requests -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set61
The whole set →Similar
Questions about analyze-feature-requests
How do I install analyze-feature-requests in Claude Code?
Run npx skills add phuryn/pm-skills --skill analyze-feature-requests -a claude-code, then run npx skills add phuryn/pm-skills --skill analyze-feature-requests -a claude-code again. The skill file is placed at ~/.claude/skills/analyze-feature-requests/SKILL.md.
What does analyze-feature-requests do?
It assesses feature requests against product goals, groups them into themes, and identifies the top 3 priorities. Each priority includes rationale, alternatives, risky assumptions, and ways to test them.
How does the skill assess customer requests?
It focuses on customer problems instead of proposed solutions and uses Opportunity Score. The score is Importance × (1 − Satisfaction), normalized to 0–1.
Source text
SKILL.md · MIT
--- 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)
© phuryn · MIT · phuryn/pm-skills