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:
Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization.
related skills
semantically similar in the cross-vendor index
don't have the plugin yet? install it then click "run inline in claude" again.
+references a concrete prioritization method (opportunity score) rather than hand-waving, grounding evaluation in a formula
+correctly distinguishes between problem discovery and solution design, avoiding common trap of outsourcing product strategy to customers
weaknesses
~procedure is incomplete: step 1 (understand goal) is listed but steps 2-5+ are missing, leaving execution path undefined
~no decision-points, output contract, or outcome signals defined - user won't know when prioritization is complete or what to do with results