AutoGineer
Generated banner for Analyze Feature Requests
Generated logo for Analyze Feature Requests

Analyze Feature Requests

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Research and analysis
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured framework for product managers to evaluate and prioritize incoming feature requests. By focusing on customer problems rather than specific feature implementations, it helps teams align their development roadmap with broader product goals. The process involves categorizing requests into themes, assessing their strategic fit, and applying evaluation criteria such as impact, effort, and risk to identify the most valuable opportunities.

What it does

  • Categorizes raw feature requests into logical themes.
  • Evaluates requests based on strategic alignment with product objectives.
  • Prioritizes the top three features using impact, effort, and risk metrics.
  • Identifies high-risk assumptions for proposed features.
  • Suggests alternative solutions to address underlying customer needs.
  • Recommends low-effort methods to test assumptions.

When to use it

  • When triaging a growing product backlog.
  • During the planning phase for upcoming product cycles.
  • When reviewing customer feedback to identify high-value opportunities.
  • When making difficult trade-off decisions regarding development resources.

Advantages

  • Prevents feature bloat by focusing on problems instead of solutions.
  • Ensures development efforts are aligned with strategic product goals.
  • Provides a clear, data-informed rationale for prioritization decisions.
  • Encourages the validation of assumptions before committing resources.

Usage examples

“Analyze these 20 user feature requests for our mobile banking app and prioritize the top 3 based on our goal of increasing user retention.”
The agent will group the requests into themes, evaluate them against the retention goal, and provide a prioritized list with rationales and testing strategies.
“I have a CSV of feedback from our CRM. Help me identify the most impactful problems to solve for our Q3 roadmap.”
The agent will parse the CSV, categorize the feedback, and present a prioritized analysis of the most significant customer problems.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/analyze-feature-requests/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip analyze-feature-requests.zip -d .agents/skills

Documentation by Pawel Huryn

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

Files

LICENSE

MIT License

Copyright (c) 2026 Pawel Huryn

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-product-discovery/skills/analyze-feature-requests · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download analyze-feature-requests.zip