MVP Definition & Validation Plan

There is a prompt instruction at https://www.zangwei.dev/prompts/product-planning/mvp-definition-validation-plan-prompt . Extract and follow the prompt to create file /docs/handbook/planning/mvp.md

You are a senior Product Manager. Design the product's **MVP (Minimum Viable Product)** definition and validation plan.

## Positioning
- The MVP goal is not "deliver a product" but "validate key assumptions"
- MVP is not the smallest feature set; it is the minimum effort that validates the biggest uncertainty
- This document bridges Planning -> Execution and is the final gate before serious investment

Based on existing conclusions, define:
1) What is the MVP?
2) How do we validate success/failure quickly with the MVP?

## General requirements
- Assumption -> validation method -> success/failure criteria
- Strictly constrain scope; avoid "let's also do X"
- Avoid implementation details; focus on validation logic
- If an assumption cannot be validated via MVP, call it out

---

## MVP output structure

1) MVP core goal
- What is the single most critical question the MVP must answer?
- If the answer is "no", should the project stop immediately?
- If successful, what further investment decisions does it enable?

2) Key assumptions (critical)
List 3–5 must-validate assumptions, e.g.:
- Do users truly have this demand?
- Do users understand and accept the core value?
- Will users pay or take the key action?
- Is the solution meaningfully better than substitutes?

For each assumption, specify:
- importance
- consequence if it fails

3) MVP scope (what to build)
- Minimum capability set required
- Explicit exclusions (what NOT to build)
- Which parts are validation tools vs long-term product assets

4) Validation path & methods
For each core assumption, define:
- method (prototype test, landing page, beta, concierge/manual ops, etc.)
- sample source and size (qual / quant)
- cycle time and required resources
- potential biases and limitations

5) Success & failure criteria (Go / No-Go)
- Success criteria per assumption
- What outcomes count as clear failure?
- Any cases where redesign is needed instead of stopping?

6) Post-MVP decision path
- If MVP succeeds, what next?
- If partially succeeds, what needs second validation?
- If fails, should we:
  - adjust positioning
  - adjust target users
  - or stop the project?

---

## Output requirements
- No technical implementation or dev schedule
- Do not cram "vision features" into MVP
- Clearly label validation purpose vs product asset
- If an effective MVP cannot be designed, call it out as a risk

End with 3–5 bullet points:
"Does this MVP truly answer the key question with minimal investment?"