# /plan - MVP Planning for Movement dApps

**Agent:** `product-manager`

Create an MVP-focused PRD with ruthlessly prioritized features for a Movement blockchain dApp.

**CRITICAL**: Build MVP first. Ship fast. Iterate later.
**CRITICAL**: Maximum 5-7 user stories for MVP. If more, scope is too big.

## Workflow

### Step 1: Understand & Challenge the Request
Analyze the user's request: $ARGUMENTS

Ask these questions:
- **Core Hypothesis** - What ONE thing are we validating?
- **Primary User** - Who is the ONE main user? (not multiple)
- **MVP Features** - What's the MINIMUM to deliver value?
- **Cut List** - What can wait for V2?

### Step 2: Apply MVP Filter
For EVERY feature mentioned, ask:
1. Can we launch without this? → If yes, CUT IT
2. Does this prove our core hypothesis? → If no, CUT IT
3. Can we add this in V2? → If yes, CUT IT

### Step 3: Define ONE Primary Persona
Pick ONE from:
- Token Holder (basic asset management)
- NFT Collector (mint/buy/sell NFTs)
- DeFi User (stake/lend/swap)
- Admin/Owner (manage dApp)

### Step 4: Create MVP PRD
Create a timestamped plan directory:

```bash
DATE=$(date +%y%m%d)
mkdir -p plans/${DATE}-{plan-name}
```

Generate: `plans/{YYMMDD}-{plan-name}/prd.md`

### Step 5: Write MVP User Stories (Max 5-7)
Only P0 stories for MVP. Everything else goes to V2 backlog.

**Format:**
- Story: "As a [persona], I want to [action], so that [benefit]"
- AC: "Given [happy path], When [action], Then [result]"

**Priority:**
- **P0 (MVP)** - Cannot launch without. Max 3-5 features.
- **P1/P2 (V2 Backlog)** - List but do NOT build yet.

### Step 6: Present MVP Summary
Present to user:
- Core hypothesis
- Primary user (ONE)
- MVP scope (3-5 features max)
- What's explicitly OUT of MVP
- Next steps (suggest `/cook` to start implementation)

## MVP Output Format

```markdown
# MVP PRD: {Feature Name}

Created: {YYMMDD}

## Core Hypothesis
{What ONE thing are we validating?}

## Problem Statement
{What ONE problem are we solving?}

## Primary User
{ONE persona and their main pain point}

## MVP Success Criteria
{1-2 measurable criteria to validate hypothesis}

## MVP Scope (P0 Only)

### In Scope (Max 5 features)
1. {Essential feature}
2. {Essential feature}
3. {Essential feature}

### OUT of MVP (V2 Backlog)
- {Deferred feature}
- {Deferred feature}

---

## MVP User Stories (Max 5-7)

### US-001: {Core Action}
**As a** {persona}
**I want to** {core action}
**So that** {benefit}

**Acceptance Criteria:**
- [ ] Given {happy path}, When {action}, Then {result}

### US-002: {Core Action}
...

---

## V2 Backlog (NOT for MVP)
- {Feature for later}
- {Enhancement for later}

## Risks & Assumptions
- {Key assumption}
```

## Scope Modes

### /plan (default)
MVP-focused planning:
- Max 5-7 user stories
- One primary persona
- Happy path only
- Ship in days

### /plan:micro
Ultra-minimal MVP:
- Max 3 user stories
- Single core feature
- Can ship in 1-2 days

## Success Criteria
- PRD has ≤7 user stories (if more, scope too big)
- ONE primary persona defined
- Clear "OUT of MVP" list
- Can be built in <2 weeks