analyze-feature-requests

Topics in the source

• Analyze Feature Requests
• Context
• Domain Context
• Instructions
• Further Reading

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: 1. Understand the goal: Confirm the product objective and desired outcomes that will guide prioritization. 2. Categorize requests into themes: Group related requests together and name each theme. 3. Assess strategic alignment: For each theme, evaluate how well it aligns with the stated goals. 4. Prioritize the top 3 features based on: Impact: Customer value and number of users affected Effort: Development and design resources required Risk: Technical and market

This is an excerpt. Refer to the complete source and its current requirements.