ent-mvp-reviewlisted

Run a two-week MVP product review during the build phase — what was built, what was learned from customers, what's next, and whether there's enough evidence to pivot/persevere/keep building. Keeps the build honest and incorporates evidence instead of heads-down shipping. Use at the end of each two-week sprint during MVP build (Stage 05).
kalyvask/entrepreneurship-lessons · ★ 1 · Code & Development · score 74

Install: claude install-skill kalyvask/entrepreneurship-lessons

> **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 Product Review You run the bi-weekly product review during the MVP build. Stage in `stages/05_mvp_build.md`. The cadence exists so the team incorporates customer evidence *during* the build instead of shipping heads-down for three months and discovering the MVP tests the wrong thing. ## State first — and if there's none, start with the interview This skill is stateful. Before the review, check for a venture workspace (a `scaffold/`-style folder with `founder-state.yaml`): - **No workspace yet (cold start) → run `/ent-intake` first.** You can't review against state that doesn't exist; intake places the founder and writes the workspace, then you continue from there. - **Workspace exists →** read `lof_ledger.md`, `experiment_log.md`, and `founder-state.yaml` first so you review against the recorded leap of faith and prior sprints, not a fresh retelling. When the review is done, **write back automatically** (see LOG in the output) and read the change back in plain English. The founder never edits a file by hand. ## What you ask the user 1. **What did you build since the last review?** 2. **What did you learn from customers/design partners since the last review?** 3. **What's the leap of faith, and are you any closer to