5d-sdd

# 5D Spec-Driven Development

A methodology for building software that prevents wasted effort by ensuring understanding before commitment at every level.

## Core Philosophy

### The 5 Dimensions

1. **Width** - Multiple domains (technical, business, user, ops, design)
2. **Depth** - Thinking levels (reactive → dogmatic → integrative → creative)
3. **Height** - Skill dependencies (what capabilities enable other capabilities)
4. **Quadrants** - Four perspectives (Individual/Collective × Inner/Outer)
5. **Time** - Evolution ("transcend and include" from current state)

### Why This Exists

Most development failures come from:
- Building before understanding
- Single-perspective thinking
- Hidden assumptions
- Spec drift from intent
- No feedback loops

5D-SDD addresses each through structured phases with explicit exit criteria.

## The 10 Phases

```
UNDERSTAND          DESIGN              BUILD               LEARN
───────────────     ───────────────     ───────────────     ───────────
0. ORIENT           2. PLAN             6. TASKS            9. REFLECT
1. SPAR             3. REFINE           7. BUILD
                    4. SPEC             8. VERIFY
                    5. GAP ANALYSIS
```

### Phase Overview

| # | Phase | Skill | What Happens | Output |
|---|-------|-------|--------------|--------|
| 0 | ORIENT | `5d-orient` | Map domains, surface assumptions | Orientation Summary |
| 1 | SPAR | `5d-spar` | Challenge thinking, find blind spots | SPAR Summary |
| 2 | PLAN | `5d-plan` | Crystallize into concrete plan | PLAN.md |
| 3 | REFINE | `5d-refine` | Stress-test, probe edge cases | Refinement Summary |
| 4 | SPEC | `5d-spec` | Formalize technical specification | SPEC.md |
| 5 | GAP | `5d-gap-analysis` | Identify all required changes | Gap Analysis |
| 6 | TASKS | `5d-tasks` | Sequence into executable tasks | Task List |
| 7 | BUILD | `5d-build` | Implement with spec fidelity | Working code |
| 8 | VERIFY | `5d-verify` | Multi-layer verification | Verification