New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Analyze Feature Requests

by phuryn in phuryn/pm-skills

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk.

MITAuto-check passedProduct & Project Management

Install Analyze Feature Requests

skills CLI
$ npx skills add phuryn/pm-skills --skill analyze-feature-requests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install phuryn/pm-skills analyze-feature-requests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pm-product-discovery/skills/analyze-feature-requests .claude/skills/analyze-feature-requests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
analyze-feature-requests
GitHub stars
27k
Token cost
~568 tokens
SKILL.md length
243 words
Files
1
Skills in repo
67
Repo updated
First seen
Licence
MIT

At a glance

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk.

  • Works in 5 steps: Understand the goal: Confirm the product… → Categorize requests into themes: Group… → Assess strategic alignment: For each… → …
  • Reviewing customer feature requests
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Triaging a backlog

What it does

Analyze Feature Requests is an agent skill from phuryn/pm-skills. 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.

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Prioritization frameworks. The repository describes itself as: PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth. The licence is MIT.

When your agent uses it

  • Reviewing customer feature requests
  • Triaging a backlog
  • Making prioritization decisions

Example prompts

  • “/analyze-feature-requests”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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
  5. For each top feature, provide

What it can do on your machine

Read from SKILL.md and the folder at commit 8607e3b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • productcompass.pm

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Analyze Feature Requests loads about 568 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 243 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~568

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from phuryn/pm-skills at commit 8607e3b, republished under its MIT licence (© phuryn). 243 words, ~568 tokens.

Download SKILL.mdSave it as .claude/skills/analyze-feature-requests/SKILL.md (or your agent's skills folder).
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

© phuryn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in pm-product-discovery/skills/analyze-feature-requests of phuryn/pm-skills.

Open the folder on GitHubat commit 8607e3b

Compare with similar skills

Analyze Feature Requests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Analyze Feature Requests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analyze Feature Requests this skillphuryn/pm-skills27k—~568Automated safety check: PassMIT
Agile Product Owneralirezarezvani/claude-skills28k3 repos~3.2kAutomated safety check: PassMIT
Prioritization Framework Advisordeanpeters/Product-Manager-Skills7.2k2 repos~4.2kAutomated safety check: PassCustom licence
Strategic Roadmap Planningdeanpeters/Product-Manager-Skills7.2k2 repos~4.7kAutomated safety check: PassCustom licence
Idea Validatoraakashg/pm-claude-skills112—~2.3kAutomated safety check: PassMIT
Triagejoa23/linear-cli144—~699Automated safety check: PassMIT

Similar skills

  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Product & Project ManagementAuto-check passed

  • Prioritization Framework Advisor

    deanpeters/Product-Manager-Skills

    Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.

    7.2k GitHub starsUsed in 2 repos~4.2k tokens
    Product & Project ManagementAuto-check passed

  • Strategic Roadmap Planning

    deanpeters/Product-Manager-Skills

    Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.

    7.2k GitHub starsUsed in 2 repos~4.7k tokens
    Product & Project ManagementAuto-check passed

  • Idea Validator

    aakashg/pm-claude-skills

    A skill your agent uses when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something.

    112 GitHub stars~2.3k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed

  • Triage

    joa23/linear-cli

    Triage and prioritize Linear backlog issues using the linear CLI.

    144 GitHub stars~699 tokensUpdated 25 days ago
    Product & Project ManagementAuto-check passed

  • Define Opportunity Tree

    product-on-purpose/pm-skills

    Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.

    715 GitHub stars~1.1k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from phuryn/pm-skills

All 67 skills in this repo

  • Agreement-Based Code Review

    phuryn/pm-skills

    Reviews a diff by anchoring on agreements between two sides of a boundary, forcing a concrete violating execution, and refuting each finding before reporting it.

    27k GitHub stars~3.6k tokensUpdated 24 days ago
    Auto-check passed

  • A/B Test Analysis

    phuryn/pm-skills

    Validates an experiment's setup, works out lift, p-value and confidence interval from A/B test data, and recommends whether to ship, extend or stop.

    27k GitHub stars~893 tokensUpdated 24 days ago
    Auto-check passed

  • Team OKR Brainstorm

    phuryn/pm-skills

    Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.

    27k GitHub stars~1.1k tokensUpdated 24 days ago
    Auto-check passed

  • Cohort Analysis and Retention Explorer

    phuryn/pm-skills

    Analyzes uploaded cohort data to compute retention curves and feature adoption trends, builds heatmaps and charts, and suggests qualitative follow-up research.

    27k GitHub stars~1.3k tokensUpdated 24 days ago
    Auto-check passed

  • Dummy Dataset Generator

    phuryn/pm-skills

    Generates realistic test datasets with custom columns, row counts and business constraints, output as CSV, JSON, SQL inserts or a runnable Python script.

    27k GitHub stars~983 tokensUpdated 24 days ago
    Auto-check passed

  • Grammar and Flow Checker

    phuryn/pm-skills

    Reviews a draft for grammar, logic and flow problems and returns located, prioritized fix suggestions without rewriting the whole text.

    27k GitHub stars~2.4k tokensUpdated 24 days ago
    Auto-check passed

Categories

Questions about Analyze Feature Requests

What does Analyze Feature Requests do?

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Analyze Feature Requests is an agent skill from phuryn/pm-skills. Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk.

When should I use Analyze Feature Requests?

Analyze Feature Requests fits situations like: reviewing customer feature requests; triaging a backlog; making prioritization decisions.

How do I install Analyze Feature Requests in Claude Code?

Run `npx skills add phuryn/pm-skills --skill analyze-feature-requests -a claude-code`. Or copy the skill folder (pm-product-discovery/skills/analyze-feature-requests in phuryn/pm-skills) into .claude/skills/analyze-feature-requests in your project. Claude Code loads it when a task matches its description.

How do I install Analyze Feature Requests in Codex?

Run `npx skills add phuryn/pm-skills --skill analyze-feature-requests -a codex`. Or copy the skill folder (pm-product-discovery/skills/analyze-feature-requests in phuryn/pm-skills) into .agents/skills/analyze-feature-requests in your project. Codex loads it when a task matches its description.

Can I use Analyze Feature Requests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add phuryn/pm-skills --skill analyze-feature-requests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-feature-requests, .gemini/skills/analyze-feature-requests, .github/skills/analyze-feature-requests and .opencode/skills/analyze-feature-requests in your project.

What does Analyze Feature Requests need to run?

SKILL.md names no scripts, command-line tools or credentials: Analyze Feature Requests is instructions for the agent only.

Does Analyze Feature Requests access the network?

SKILL.md names 1 domain. As links in the text: productcompass.pm. This is read from the text; nothing was executed.

Is Analyze Feature Requests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Analyze Feature Requests use?

Analyze Feature Requests is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Analyze Feature Requests use?

About 568 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Analyze Feature Requests?

Skills that share tags, products or a category with Analyze Feature Requests: Agile Product Owner (alirezarezvani/claude-skills, 28k stars), Prioritization Framework Advisor (deanpeters/Product-Manager-Skills, 7.2k stars), Strategic Roadmap Planning (deanpeters/Product-Manager-Skills, 7.2k stars) and Idea Validator (aakashg/pm-claude-skills, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyze Feature Requests?

phuryn (a GitHub user) maintains it in phuryn/pm-skills, which has 26,845 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on September 14, 2026.

Source: phuryn/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.