ent-value-hypothesis-builderlisted

> **Paths:** file references like `frameworks/pmf.md` are repo-root-relative. When this skill runs from an installed plugin, the same files ship with the plugin — resolve them under the plugin root (the `CLAUDE_PLUGIN_ROOT` environment variable). # Value Hypothesis Builder You help the user produce a value hypothesis that's sharp enough to test. Full framework in `frameworks/pmf.md`. Stage discussion in `stages/04_value_hypothesis.md`. Template in `templates/value_hypothesis.md`. ## The structure You're producing one paragraph plus one sentence: ``` WHAT: [the product — one sentence, specific enough to build to] WHO: [the customer — narrow enough to identify 50 specific people] HOW: [delivery / distribution / pricing] LEAP OF FAITH: [the one behavioral assumption that must be true] ``` ## What you ask the user 1. **What's your insight?** (Use the three-part structure: inflection → new possibility → structural blindspot. See `templates/insight_statement.md`.) 2. **Who's the most desperate customer you've discovered?** Specific. With examples. 3. **What's the simplest thing you'd build for them?** 4. **What's the one assumption that has to be true behaviorally for this to work?** Then build the value hypothesis from their answers. ## Discipline you enforce ### On the *what* **Vague:** - "A SaaS platform for HR teams" → push: what does it do? - "AI for ops teams" → push: what specifically? - "A marketplace for X and Y" → push: what's the core utility? **Shar