agentmods.dev

analyze-feature-requests

analyze-feature-requests is a skill for Claude Code from yuusakuri/agent-skills. It costs 45 tokens per session (476 once invoked), scanned A, a copy of analyze-feature-requests, MIT.

A method for sorting and ranking customer feature requests by shared theme, product fit, expected impact, effort, and risk.

In plain words
What is it for?
Use it to review a feature backlog, group similar requests, identify the most important customer problems, and recommend priorities.
Why use it?
It turns a long request list into a clearer order of problems to address without letting customers dictate the solution.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

not rated 2repo 14d ago A scan 45 tokens copy · 100% MIT

Good fit Use it to review a feature backlog, group similar requests, identify the most important customer problems, and recommend priorities.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yuusakuri/agent-skills/analyze-feature-requests
View source ↗ yuusakuri/agent-skills
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 yuusakuri/agent-skills --skill analyze-feature-requests
Clone the repo
git clone --depth 1 https://github.com/yuusakuri/agent-skills

Made for: Claude Code.

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.

agentmods badge for analyze-feature-requests

README.md
[![agentmods](https://agentmods.dev/badge/skills/yuusakuri/agent-skills/analyze-feature-requests/github.svg)](https://agentmods.dev/skills/yuusakuri/agent-skills/analyze-feature-requests)
Your own site
<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/analyze-feature-requests"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-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.

agentmods 80×15 button for analyze-feature-requests

Your own site · 80×15
<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/analyze-feature-requests"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-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.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce 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 2mo 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 2mo 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

This is a copy

100% identical to analyze-feature-requests — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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:

  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

Read the full file on GitHub · 50 lines

Changes

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.

  1. 2mo 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 yuusakuri/agent-skills (2 stars, last pushed 14d 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. It is 100% identical to analyze-feature-requests, differing in 0 lines, and is treated as a copy.

PlanningProject management
Related

analyze-feature-requests compared with skills from other repositories

analyze-feature-requests next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
analyze-feature-requestsyuusakuri/agent-skillsSkill214d agoMITA45Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code