What problem does it solve? Before customer interviews, founders and PMs hold unwritten assumptions that confirmation bias silently protects. This Skill draws out those beliefs, sharpens them into numbered, falsifiable hypotheses (H1, H2, ...) mapped to goal questions, and preserves them in a HYPOTHESES.md file so interviews can confirm or contradict them. ## Core Features & Use Cases - Goal-driven elicitation: Reads a GOALS.md goal-question list and walks it one goal at a time, drawing out the user's own beliefs rather than generating answers for them. - Falsifiability rubric: Critiques draft hypotheses for specificity, testability, single claims, goal coverage, and whether resolving each one would change a real decision. - Resumable artifact: Writes HYPOTHESES.md incrementally with an in-progress status note, so sessions can resume exactly where they stopped. - Use Case: A founder with a list of eleven goal questions about a hosting market uses this Skill to record eighteen numbered hypotheses with thresholds like "$50/mo" and "100,000 page-views," each tagged to the goals it addresses, before writing any interview questions. ## Quick Start Run the asb-interview-hypotheses skill on my GOALS.md to help me write down my customer hypotheses before interviewing.
