What problem does it solve? Product teams often write lengthy speculative specifications before validating whether an idea will succeed. This Skill replaces documentation-as-validation with a rapid empirical loop that tests the single make-or-break assumption across users, market, and technology before committing engineering resources. ## Core Features & Use Cases - Essential Question Framing: Inverts assumptions into one falsifiable question that determines product success or failure. - 3-Variable Intersection Mapping: Analyzes Users (behavior and friction), Market (willingness to pay and unit economics), and Technology (feasibility and latency constraints). - Test Vehicle Dispatching: Selects the cheapest validation method, such as a 24-hour facade prototype, smoke test landing page, 1-day technical spike, or 14-day A/B experiment. - Use Case: Before building an AI contract redlining tool, generate a hypothesis card with pre-committed Pass/Pivot/Kill thresholds, run five user interviews against a disposable prototype, and graduate validated findings into a PRD. ## Quick Start Run the empirical product hypothesis loop for my new feature idea by defining the essential question, mapping users, market, and technology, and selecting the fastest test vehicle.
