Turn scattered feature requests into a prioritized list based on actual demand.
4-6 hrs → 10 min
Compared to doing it manually
/feature-request-analyzerType this in Claude to run the skill
Requests are everywhere. Some ideas appear 50 times, others once from a loud customer.
.claude/skills/ folder in your project/feature-request-analyzer in Claude to run the skillExtract Jobs-to-be-Done statements from research data to uncover innovation opportunities.
Transform interview transcripts into structured insights with quotes, patterns, and recommendations.
Analyze and categorize customer feedback into actionable themes using affinity mapping.
Extract themes, complaints, and feature requests from app reviews at scale.
Don't just count requests — understand the underlying problems. Group by job-to-be-done, identify patterns, consider requester segments, and estimate impact. One enterprise request might outweigh 100 free user requests.
Not always. Users describe solutions, not problems. Dig into WHY they want it. Often the underlying need can be solved better than the requested feature. "If I had asked people what they wanted, they would have said faster horses."
Download this skill and drop it in your .claude/skills/ folder.
This skill + 70+ more, context files, and agent workflows — $499