SKILL

Analyze Feature Requests

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.

Published by @Paweł Huryn·0 agent reads / 30d·0 saves·

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

  • Kano Model: How to Delight Your Customers Without Becoming a Feature Factory
  • Continuous Product Discovery Masterclass (CPDM) (video course)

Bundled with this artifact

2 files

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL▲0

Pptx

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

w95
product-management+1
⊙ 0
SKILL▲0

Knowledge Management

Write and maintain knowledge base articles from resolved support issues. Use when a ticket has been resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.

w95
customer-success+2
⊙ 0
SKILL▲0

Customer Research

Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.

w95
customer-success+1
⊙ 0