Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From pm-product-discovery
Analyzes and prioritizes feature requests by theme, strategic alignment, impact, effort, and risk. Use for customer request reviews, backlog triaging, or prioritization.
npx claudepluginhub phuryn/pm-skills --plugin pm-product-discoveryHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-product-discovery:analyze-feature-requestsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Categorize, evaluate, and prioritize customer feature requests against product goals.
Analyzes feature request lists by themes, strategic alignment, impact, effort, risk to prioritize top features. Use for customer request reviews, backlog triage, product prioritization.
Applies RICE, MoSCoW, Kano, ICE, and Opportunity Scoring frameworks to rank features and backlog items. Produces scored tables, build order, and deprioritised items.
Provides MoSCoW, Kano Model, WSJF, and Wiegers' matrix for prioritizing requirements by business value, customer impact, effort, and risk. Includes scoring templates and trade-off analysis.
Share bugs, ideas, or general feedback.
Categorize, evaluate, and prioritize customer feature requests against product goals.
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.
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.
The user will describe their product goal and provide feature requests. Work through these steps:
Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization.
Categorize requests into themes: Group related requests together and name each theme.
Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals.
Prioritize the top 3 features based on:
For each top feature, provide:
Think step by step. Save as markdown or create a structured output document.