Skip to main content
skill Claude Code CX Codex Cursor GitHub Copilot

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add phuryn/pm-skills --skill analyze-feature-requests -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/analyze-feature-requests/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/analyze-feature-requests/

From the same set61

The whole set →
create-prd phuryn This skill builds a lean PRD from an 8-section template. Use it to define a feature, document product requirements, or review an existing PRD. Claude Code CX Codex Cursor +1 10,800installs pre-mortem phuryn Runs a pre-mortem risk assessment on PRDs and launch plans. Catches critical launch blockers, surfaces hidden team assumptions, and maps action items. Claude Code CX Codex Cursor +1 10,200installs outcome-roadmap phuryn Rewrites feature-heavy roadmaps into outcome-focused statements tied to business and customer impact. Helps teams replace rigid feature lists with measurable strategic goals. Claude Code CX Codex Cursor +1 9,900installs prioritization-frameworks phuryn Reference guide to 9 prioritization frameworks: RICE, ICE, Opportunity Score, Kano, MoSCoW and more. Helps you pick the right method, compare approaches, and rank tasks by importance. Claude Code CX Codex Cursor +1 9,900installs strategy-red-team phuryn Stress-tests PRDs, roadmaps, and strategies by attacking load-bearing assumptions before reality does, returning kill criteria and cheap tests. Claude Code CX Codex Cursor +1 9,200installs competitor-analysis phuryn This skill researches direct competitors and compares their positioning, strengths, weaknesses, and pricing. Use it to prepare a competitive brief or find ways to differentiate a product. Claude Code CX Codex Cursor +1 3,800installs business-model phuryn Skill generates a Business Model Canvas with all 9 building blocks: from key partners and activities to channels and revenue streams. Use it to create a business model, document how value flows, or analyze an existing business. Claude Code CX Codex Cursor +1 3,700installs privacy-policy phuryn Skill drafts a detailed privacy policy accounting for GDPR, CCPA, and other regulations. Use it when building a new product, updating data protection docs, or preparing for compliance audits. Claude Code CX Codex Cursor +1 3,500installs

Similar

apple-notes Hermes Agent Lets a coding agent read, search and write Apple Notes from the terminal through the memo CLI, with everything syncing over iCloud. Claude Code CX Codex Cursor +1 381installs airtable community Ready-made curl calls for Airtable's REST API: read records, filter with formulas, write in batches, upsert on a merge field. Claude Code CX Codex Cursor +1 375installs apple-reminders Hermes Agent Manages Apple Reminders through the remindctl CLI utility. Enables the assistant to read task lists and schedule items with iCloud sync. Claude Code CX Codex Cursor +1 367installs teams-meeting-pipeline Hermes Agent + Teknium Manages Microsoft Teams meeting summaries, transcript ingestion, and Graph webhook subscriptions. Useful for replaying failed jobs and checking pipeline health. Claude Code CX Codex Cursor +1 365installs find-community slavingia A skill that helps you find the community you already belong to and spot problems worth solving for a minimalist business. Use it when searching for a startup idea or unsure where to start as an entrepreneur. Claude Code CX Codex Cursor +1 2,600installs find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. Claude Code CX Codex Cursor +1 4,000,000installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. Claude Code 1,424,476installs grill-with-docs Matt Pocock This skill interviews you about a plan or design and creates ADRs and a glossary along the way. Use it when decisions need sharper definition. Claude Code 1,219,756installs

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

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor