analyze-feature-requests

analyze-feature-requests helps product teams categorize, evaluate, and prioritize customer feature requests against product goals. It solves the feature-factory problem by shifting focus from individual customer-requested features to underlying opportunities (problems), so teams do not simply build whatever customers ask for. If the user provides files such as spreadsheets, CSVs, or documents containing feature requests, the skill reads and analyzes them directly and may create a summary table for structured data.

The skill works through a defined sequence. First it confirms the product objective and desired outcomes that guide prioritization. It then groups related requests into named themes and assesses how well each theme aligns with the stated goals. It prioritizes the top three features based on Impact (customer value and number of users affected), Effort (development and design resources required), Risk (technical and market uncertainty), and strategic alignment with the product vision. For each top feature it provides a rationale grounded in customer needs and strategic fit, alternative solutions worth considering, the high-risk assumptions involved, and how to test those assumptions with minimal effort. It draws on the Opportunity Score from Dan Olsen (Opportunity Score = Importance x (1 - Satisfaction), normalized to 0-1) to evaluate customer-reported problems, and points to the prioritization-frameworks skill for full details and templates.

It targets product managers reviewing customer feature requests, triaging a backlog, or making prioritization decisions. A guiding principle is to never let customers design solutions, and instead prioritize problems over features. The skill recommends thinking step by step and saving output as markdown or a structured document, and links to further reading including the Kano Model and the Continuous Product Discovery Masterclass.