What problem does it solve? Product teams often commit to building features before validating that a real customer problem exists, leading to wasted development effort and low adoption. This Skill provides a structured, multi-phase discovery workflow that takes a rough problem hypothesis through framing, customer interviews, synthesis, solution experiments, and a documented go/no-go decision. ## Core Features & Use Cases - Six-Phase Orchestration: Coordinates problem framing, research planning, customer interviews, insight synthesis, solution experiments, and decision documentation over 2-4 weeks. - Decision Gates: Built-in checkpoints for research saturation, hypothesis validation, and go/pivot/kill outcomes prevent premature commitment. - Skill Composition: Invokes component skills like problem-framing-canvas, discovery-interview-prep, opportunity-solution-tree, and prd-development at the right phase. - Use Case: A PM investigating a 15% activation-rate drop runs the workflow: frames the problem, interviews 7 churned users, synthesizes pain points via affinity mapping, tests a guided-checklist prototype, and documents a validated GO decision with an epic hypothesis. ## Quick Start Run discovery on this hypothesis: SMB admins abandon onboarding because the data-import step requires IT help they don't have.
