What problem does it solve? Teams routinely ship features users never adopt because interviews pitch the idea instead of testing real behavior, and there is no falsifiable hypothesis to fail against. This Skill runs a disciplined five-phase validation workflow that converts user interviews into an evidence-based build, iterate, or kill decision before engineering invests. ## Core Features & Use Cases - Hypothesis Definition: Forces a written one-page hypothesis with target segment, current workaround, signal thresholds, and kill criteria before any interviews begin. - Mom Test Interview Guides: Generates 8-12 question scripts that probe past behavior and current workarounds, automatically rewriting leading or hypothetical questions. - Decision Synthesis: Aggregates interviews against thresholds, maps JTBD Forces of Progress (push, pull, anxiety, habit), and builds a mini Opportunity Solution Tree to produce a BUILD, ITERATE, or KILL verdict. - Use Case: Before writing a PRD for a Smart Follow-Up feature, run 8-12 interviews with target users, capture their actual workarounds and switching anxieties, and receive a decision document stating whether to build, reshape, or kill the idea. ## Quick Start Ask the assistant to validate whether a planned feature is worth building by running pre-build user interviews before writing the PRD.
