5d-plan

# PLAN Phase

Crystallize sparring outcomes into a concrete plan.

## Plan Structure

### 1. Problem Statement

One paragraph. What problem does this solve? For whom? Why now?

Avoid: Solution-focused framing. This section is about the problem, not the answer.

### 2. Proposed Solution

Describe what will exist that doesn't exist now. Use plain language—no technical jargon yet.

Include:
- Core functionality (what it does)
- Key behaviors (how it works from user perspective)
- Boundaries (what it explicitly won't do)

### 3. Assumptions & Bets

Make implicit assumptions explicit:

```
We assume:
- [assumption about users]
- [assumption about technical feasibility]
- [assumption about business value]

We are betting that:
- [bet 1 - what we're gambling on]
- [bet 2]

Identity attachment risk:
- [what we might be defending rather than evaluating]
```

### 4. Thinking Level Declaration (Depth)

Acknowledge current thinking level:
- Are we at Level 2 (dogmatic—"this is the right way")?
- Can we articulate why alternative approaches might be valid (Level 3)?
- What novel insight does this plan contain (Level 4)?

### 5. Skill Dependencies (Height)

Document what capabilities the plan requires:
- What skills must the team have or acquire?
- What domain knowledge unlocks implementation?
- What's blocking progress that's outside this plan's scope?

### 6. Alternatives Considered

Document what was rejected and why:

| Alternative | Why Rejected |
|-------------|--------------|
| [option A] | [reason] |
| [option B] | [reason] |

This prevents re-litigating decisions later.

### 7. Quadrant Coverage

Ensure plan addresses all four:

| Quadrant | Plan Element |
|----------|--------------|
| Individual Outer | What artifacts will be created |
| Individual Inner | What understanding/skills are required |
| Collective Outer | How this fits existing systems |
| Collective Inner | What alignment is needed across stakeholders |

### 8. Time Horizons

- **V1 (this iteration):** [sco