What problem does it solve? Product teams often jump straight to building features without validating which customer problem is worth solving, wasting effort on the wrong opportunities. This Skill structures product discovery using Teresa Torres' Opportunity Solution Tree method, connecting one measurable outcome to customer opportunities, candidate solutions, and fast experiments. ## Core Features & Use Cases - Outcome Definition: Guides the team to articulate a single measurable outcome (e.g., raise 7-day retention from 20% to 35%) and rejects vague or solution-shaped goals. - Opportunity Mapping and Scoring: Frames 3-7 customer needs from research and prioritizes them with Dan Olsen's Opportunity Score (Importance × (1 − Satisfaction)). - Solution Divergence and Experiment Design: Generates at least 3 solutions per opportunity from PM, design, and engineering angles, then designs cheap experiments (A/B tests, fake doors, prototypes) testing value, usability, feasibility, and viability assumptions. - Use Case: A CTO asks what to build to improve conversion. The Skill produces a docs/discovery/OST-conversion.md document with a scored opportunity map, solution tables, and an experiment backlog that feeds directly into a PRD. ## Quick Start Ask the assistant to build an Opportunity Solution Tree for improving your target metric, providing any customer research or feedback you have.
