What problem does it solve? Teams often jump straight to building solutions without framing the underlying business problem, surfacing risky assumptions, or defining what to learn first. This Skill structures that conversation using Jeff Gothelf's Lean UX Canvas v2, turning assumptions into cheap experiments before development begins. ## Core Features & Use Cases - Eight-box guided facilitation: Walks through Business Problem, Business Outcomes, Users, User Outcomes, Solutions, Hypotheses, Riskiest Assumption, and Smallest Experiment, with a checkpoint gate after each box. - Upstream artifact collapse: When PROBLEM_STATEMENT.md and PROTO_PERSONA.md exist, it pre-fills Boxes 1, 3, and 4 and starts the real conversation at Box 2. - Experiment contract enforcement: Box 8 is only complete with a method, a pre-stated pass/fail signal, and a timebox, and Boxes 7-8 loop until confidence is high enough to build. - Use Case: A product team debating a new in-app dispute feature uses the canvas to discover their riskiest assumption is a value assumption (does visible status deflect calls?), then designs a two-week IVR experiment with no engineering build to test it. ## Quick Start Ask the assistant to run a Lean UX Canvas session for your initiative, starting from the business problem and your target user.