prioritize-features

Evaluate each feature against impact, effort, risk, and strategic alignment with your product objective, then rank the results. This Skill walks through that evaluation and returns a top 5 list with rationale, trade-offs, and deprioritization notes.

ICE scores initiatives as Impact × Confidence × Ease, where Impact can combine Opportunity Score with customer count. RICE adds Reach as a separate factor, making it better suited for larger teams that need to account for how many users each feature touches.

Opportunity Score comes from Dan Olsen's The Lean Product Playbook and equals Importance × (1 − Satisfaction), normalized to 0–1. High importance combined with low satisfaction signals the best customer problems to prioritize, focusing on opportunities rather than solutions.

Yes, you can provide spreadsheets, backlogs, or opportunity assessments as input files, and they will be read and analyzed directly. You should also state your product objective and desired outcomes so the evaluation criteria are grounded.

Scoring-based prioritization is less useful when you lack any customer data or a clear product objective, since the scores become guesses. In that case, gather customer importance and satisfaction data first so Opportunity Score and impact estimates have a basis.