prioritize-features

原文涵盖的主题

• Prioritize Feature Backlog
• Context
• Domain Context
• Instructions
• Further Reading

Evaluate and rank a backlog of feature ideas to identify the top 5 to pursue. You are helping prioritize features for $ARGUMENTS. If the user provides files (spreadsheets, backlogs, opportunity assessments), read and analyze them directly. For framework selection guidance, see the prioritization-frameworks skill. Key recommendations: Opportunity Score (Dan Olsen, The Lean Product Playbook) is recommended for evaluating customer problems: Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1. High Importance + low Satisfaction = best opportunities. Prioritize problems (opportunities), not solutions. ICE is recommended for quick scoring of initiatives: Impact (Opportunity Score × # Customers) × Confidence × Ease. RICE adds Reach as a separate factor for larger teams. The user will describe their product objective, desired outcomes, and provide feature ideas. Work through these steps: 1. Understand priorities: Confirm the product objective and success metrics. 2. Evaluate each feature against: Impact: How much does it move the needle on desired outcomes? Consider Opportunity Score if customer data is available. Effort: How much development, design, and coordination is

这里只展示节选，请以完整原文和当前要求为准。