analyze-feature-requests
by phurynAnalyze and prioritize feature requests by theme, strategic fit, impact, effort, and risk with the analyze-feature-requests skill. Use it to review customer feedback, triage a backlog, and make defensible product decisions, including analyze-feature-requests for Competitive Analysis when comparing demand across competitors.
This skill scores 78/100, which means it is a solid listing candidate for Agent Skills Finder: it gives agents a clear trigger, a defined prioritization workflow, and enough domain guidance to reduce guesswork compared with a generic prompt. Directory users can reasonably install it if they need a reusable feature-request triage workflow, though they should expect some missing operational extras.
- Clear trigger and use case for analyzing or triaging feature requests, including when files like spreadsheets or CSVs are provided.
- Concrete step-by-step workflow covering goal understanding, theme grouping, strategic alignment, and top-3 prioritization.
- Includes product-discovery guidance that pushes agents toward opportunity/problem framing and references Opportunity Score.
- No supporting scripts, references, or companion files, so agents rely entirely on the SKILL.md text for execution.
- The excerpted instructions are somewhat incomplete at the end and there is limited practical detail on outputs, edge cases, or scoring implementation.
Overview of analyze-feature-requests skill
The analyze-feature-requests skill helps you turn a raw list of customer asks into a structured prioritization view. It is best for product managers, founders, UX researchers, and support or success teams who need to decide what to build next, not just summarize feedback. If you need the analyze-feature-requests skill to compare requests by theme, strategic fit, impact, effort, and risk, this is the right workflow.
What this skill is for
Use analyze-feature-requests when you have customer feedback in spreadsheets, CSVs, notes, tickets, or documents and need a decision-oriented synthesis. The real job is to identify repeated problems, separate opportunities from solution ideas, and rank what matters most to the product goal.
Why it differs from a generic prompt
A generic prompt often produces a loose summary of requests. This skill pushes toward disciplined grouping, opportunity framing, and prioritization logic. That matters when the backlog is noisy, requests conflict, or stakeholders want a defendable shortlist rather than a theme dump.
Best fit and misfit cases
This skill fits backlog triage, roadmap review, and competitive analysis of what customers are asking for. It is a weaker fit if you already have a fixed scoring model, if the input is only one or two requests, or if the task is to design a solution in detail instead of evaluating demand.
How to Use analyze-feature-requests skill
Install and load the skill
Run npx skills add phuryn/pm-skills --skill analyze-feature-requests to install the skill. The analyze-feature-requests install step is simple, but the output quality depends on giving the agent a clear product goal and a clean request set.
Give the skill the right input
For strong analyze-feature-requests usage, provide: the product objective, the audience, the time horizon, and the raw feature requests. If your source is messy, include the original wording plus any metadata you trust, such as customer segment, deal size, frequency, or severity. Example input shape: “Optimize onboarding conversion for SMB admins; analyze these 42 support-derived requests and prioritize the top opportunities.”
Read the repo files in order
Start with SKILL.md, then inspect any linked context files your environment exposes, especially README.md, AGENTS.md, metadata.json, or supporting folders such as rules/, resources/, and references/. In this repository, the skill is compact, so SKILL.md is the main source of truth; the next step is to adapt the method to your own data, scoring criteria, and decision cadence.
Workflow tips that improve output
Ask for themes first, then ranking, then rationale. For better analyze-feature-requests guide results, tell the model to group requests into opportunities, not feature names, and to note when the input is actually a solution request disguised as a problem. If you are using analyze-feature-requests for Competitive Analysis, provide competitor names and the customer pains they appear to solve so the comparison stays grounded in demand, not marketing claims.
analyze-feature-requests skill FAQ
Is this skill better than a plain prompt?
Usually yes, if you need repeatable prioritization rather than one-off summarization. The analyze-feature-requests skill adds a structured workflow that makes the result easier to defend in a planning meeting.
Does it support spreadsheets or CSVs?
Yes. The repository guidance says to read structured files directly and, when useful, summarize them in a table. That makes it practical for support exports, survey dumps, or backlog sheets.
Can beginners use it?
Yes, if they can state a product goal and provide the source requests. The skill is most useful when someone can clarify what “good” looks like, because prioritization depends on context more than on request volume.
When should I not use it?
Do not use it when you want implementation design, technical architecture, or a final roadmap commitment. It is meant to analyze and prioritize demand, not to replace product judgment or downstream execution planning.
How to Improve analyze-feature-requests skill
Provide stronger context up front
The biggest quality lever is the goal statement. Instead of “analyze these requests,” say what outcome matters, such as retention, activation, revenue expansion, or support load reduction. The more explicit the objective, the better the strategic alignment and prioritization reasoning.
Include request-level signals
Add frequency, account type, customer tier, churn risk, deal impact, or timestamps when available. Those signals help the model distinguish one loud request from a repeated opportunity and make the analyze-feature-requests skill far more useful for competitive analysis or roadmap tradeoffs.
Ask for the output format you need
If you need a decision artifact, request a theme table, a top-3 ranking, and a short rationale for each. If you need an internal working doc, ask for assumptions, open questions, and what information would change the ranking. Iterating on format usually improves clarity faster than asking for “more detail.”