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.
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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/analyze-feature-requests · pinned to the source commit
# Run from your project root
git clone https://github.com/phuryn/pm-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 18468a95b427e70e258b51389796367c6f684e7d
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/pm-product-discovery/skills/analyze-feature-requests" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/phuryn/pm-skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 18468a95b427e70e258b51389796367c6f684e7d
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/pm-product-discovery/skills/analyze-feature-requests" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/analyze-feature-requests
Scanner static-checks@0.1.0 · commit 18468a95b427. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.