analyze-feature-requests helps the agent triage a pile of customer requests against your product goal. It confirms the goal, groups requests into named themes, rates each theme’s strategic alignment and then picks the top three features.
For each top feature it gives the rationale, alternative solutions, high-risk assumptions and a low-effort way to test them. The skill leans on Opportunity Score from Dan Olsen and tells the agent to prioritize the underlying problems, since customers should not design the solutions.
What You Get
- Feature requests grouped into named themes
- A strategic alignment assessment for each theme
- A top three list scored on impact, effort, risk and strategic fit
- Rationale, alternative solutions and high-risk assumptions per top feature
- A cheap way to test each risky assumption
- An optional summary table or markdown document
Common Use Cases
- Triaging a quarter of customer requests before roadmap planning
- Turning a CSV export from a support or CRM tool into themes
- Explaining to a stakeholder why a loud request ranks lower
- Finding the problem behind several differently worded requests
What Makes It Unique
It frames requests as signals about opportunities (problems) and cites the Opportunity Score formula, importance times one minus satisfaction, normalized to a 0 to 1 scale, as the lens. Every top pick comes with the assumptions to test and a cheap test for each, which links triage to discovery work. It points to the prioritization-frameworks skill for templates and full framework details.
Under The Hood
A single SKILL.md of instructions with no scripts. The agent reads any spreadsheet, CSV or document you attach with its own file tools, and the skill says to save the result as markdown or a structured output document, so it can write a file. It does not tell the agent to fetch web pages, call APIs or run commands. Your product goal replaces $ARGUMENTS in the prompt.