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.
Install
git clone https://github.com/phuryn/pm-skills /tmp/pm-skills && ln -s /tmp/pm-skills/pm-product-discovery/skills/analyze-feature-requests ~/.claude/skills/analyze-feature-requestsFrom README
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. Categorize requests into themes: Group related requests together and name each theme.
More from this repo
intended-vs-implemented
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of...
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping.
strategy-red-team
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does.