What problem does it solve? Stakeholder requests arrive as solutions ("add a filter button") with no visible outcome or customer problem behind them, so teams commit to building before framing the problem. This Skill ladders a request up to a measurable product outcome, maps the opportunity space in between, and produces a tree plus one assumption test. ## Core Features & Use Cases - Request-to-outcome laddering: Converts a feature request, mandate, or vague OKR into a single measurable product outcome the team can move. - Opportunity/solution discrimination: Applies five sniff tests (customer's mouth, UI noun, pre-existence, doneness, so-what) to separate customer needs from disguised solutions. - Sibling comparison and assumption testing: Selects exactly one target opportunity by comparing siblings on sizing, market, company, and customer factors, then designs an assumption test with a pass signal fixed in advance. - Use Case: A Head of Customer Service asks for a filter button on the transaction list. The Skill ladders down to "I cannot find the dispute I opened last week", generates four candidate solutions, places the original request as one leaf in the tree, and outputs an ASCII tree plus a test card ready to paste into a ticket. ## Quick Start Ask the assistant to turn a stakeholder feature request into an opportunity solution tree with one target opportunity and a first assumption test.
