Define MVP scope using MoSCoW prioritization. Identify Must-haves, technical prerequisites, and create a launch milestone with timeline. Triggers: MVP, minimum viable, first release, initial scope, launch scope
Define the minimum viable product scope for a project or feature set.
Categorize every item:
| Priority | Meaning |
|---|---|
| Must | Launch blocker — product is broken without it |
| Should | High value but launch can proceed without it |
| Could | Nice-to-have, low effort |
| Won't | Explicitly deferred — not in this release |
For each item, justify the category in one sentence.
v0.1 — MVP).Produce a structured document:
## MVP Definition: [Project Name]
### All Features (MoSCoW)
| Feature | Priority | Justification |
|---------|----------|---------------|
### MVP Scope (Must-haves)
- ...
### Technical Prerequisites
- ...
### Milestone: [Name]
- Target date: [date]
- Critical path: [items]
- Deliverables: [list]
Save to plan/ or present to the user for review.