What problem does it solve? Product teams often start building on untested assumptions, invented research, or vague stakeholder requests. This Skill structures a product discovery conversation that separates observations, decisions, and hypotheses, then records the result in a rigorous product brief that downstream skills can trust. ## Core Features & Use Cases - Structured discovery interviews: Runs bounded question rounds in three modes (existing product, client idea, own idea), asking only questions that could change the current decision. - Evidence-disciplined brief: Writes product-brief.md with source-tagged claims ([INTERVIEW], [DATA], [DOCUMENT], [PRODUCT], [BENCHMARK], [SYNTHETIC], [ASSUMPTION]), stable decision/rule/non-goal ids, and a collection plan for missing material. - Independent skeptical review: Passes the draft to a fresh-context subagent that checks source fidelity, problem/solution fit, and readiness before anything is written. - Use Case: A founder with a new SaaS idea runs a discovery session; the Skill interviews them, tags every claim by evidence tier, records confirmed decisions with owners, and produces a brief that honestly states which assumptions remain untested. ## Quick Start Ask the assistant to run a product discovery session for your idea or existing product and produce a product brief.