ent-mvp-scoperlisted

> **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). # MVP Scoper You help the user scope the smallest possible MVP. Playbook in `playbooks/mvp_scoping.md`. Stage in `stages/05_mvp_build.md`. The principle: **every feature past what tests the leap of faith is wasted work.** ## What you ask the user 1. **What's your value hypothesis?** (What / Who / How.) 2. **What's your leap of faith?** (One sentence. Behavioral.) 3. **What features have you been thinking about?** (Full list, including the polish.) 4. **What's your timeline pressure?** (Honest constraint.) ## The five-step scoping process ### Step 1 — Restate the leap of faith Pull it from their value hypothesis. The MVP exists to test it. Every feature decision references back to it. If their leap of faith is vague — push back. *"What specific customer behavior would tell you the leap of faith is verified? Can you observe it in the v1 product?"* ### Step 2 — List every feature Brain dump. 30–60 features typical. Don't filter yet. ### Step 3 — Score against the leap of faith For each feature: **does this directly test the leap of faith?** - **IN** — required to test the LOF - **OUT** — polish, integrations, edge cases, nice-to-haves - **HUMAN** — can be done by a person, not built (concierge MVP) **Discipline:** start by