What is analyze-feature-requests?

A framework for grouping and ranking feature requests by theme, product goals, customer impact, effort, and risk. It focuses on the customer problem behind a request rather than treating every suggested feature as the solution.

Use it to analyze a request list, compare opportunities, and identify the highest-priority work.

It helps teams make consistent prioritization decisions instead of choosing based only on who asked or how often. It also shows which requests best support the product's goals.

analyze-feature-requests — Skill for Claude Code by phuryn/pm-skills

About the project

phuryn/pm-skills is a marketplace of reusable skills, commands, and plugins that guide AI assistants through product-management work such as discovery, strategy, planning, metrics, launches, and growth. It is for product managers and teams using Claude Code, Cowork, or compatible assistants. The catalogue entries are the project's own workflows and extensions.

phuryn/pm-skills · 27,719 stars · on GitHub · productcompass.pm

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add phuryn/pm-skills --skill analyze-feature-requests

Clone the repo

git clone --depth 1 https://github.com/phuryn/pm-skills

Made for: Claude Code.

Or install pm-product-discovery, the plugin that ships this one along with the rest of its 13 skills, 5 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/phuryn/pm-skills/analyze-feature-requests/github.svg)](https://agentmods.dev/skills/phuryn/pm-skills/analyze-feature-requests)

Your own site

<a href="https://agentmods.dev/skills/phuryn/pm-skills/analyze-feature-requests"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/analyze-feature-requests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/phuryn/pm-skills/analyze-feature-requests"><img src="https://agentmods.dev/badge/skills/phuryn/pm-skills/analyze-feature-requests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 476 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 15 Sept 2026
Snyk pass 15 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.00476
Opus 5.5	$0.00018	$0.00190
Sonnet 5.5	$0.00009	$0.00095
Haiku 4.5	$0.00005	$0.00048

Measured 1mo ago against content hash 7615db7687a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analyze-feature-requests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

analyze-feature-requests — 100% identical, 0 lines differ

pm-product-discovery/skills/analyze-feature-requests/SKILL.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 50 lines · 45 tokens per session scan A 7615db7687a6

Subscribe to this mod's changes

analyze-feature-requests is a skill published in the GitHub repository phuryn/pm-skills (27,719 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 476 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-15.

Planning Project management agent-skill-repository agent-skills agentic-skills claude-code-marketplace claude-code-plugins product-management

analyze-feature-requests next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
analyze-feature-requestsphuryn/pm-skills	Skill	28k	8d ago	MIT	A	45	Claude Code
becoming-senior-pmProductfculty-aipm/PM-Copilot-by-Product-Faculty	Skill	80	6mo ago	none	A	126	Claude Code
founding-pmProductfculty-aipm/PM-Copilot-by-Product-Faculty	Skill	80	6mo ago	none	A	106	Claude Code
technical-pmProductfculty-aipm/PM-Copilot-by-Product-Faculty	Skill	80	6mo ago	none	A	109	Claude Code
ai-feature-monetizationProductfculty-aipm/PM-Copilot-by-Product-Faculty	Skill	80	6mo ago	none	A	89	Claude Code
altitude-horizonProductfculty-aipm/PM-Copilot-by-Product-Faculty	Skill	80	6mo ago	none	A	85	Claude Code
attitudinal-segmentationProductfculty-aipm/PM-Copilot-by-Product-Faculty	Skill	80	6mo ago	none	A	83	Claude Code

analyze-feature-requests