c3-provision

# C3 Provision - Architecture Without Implementation

**Document architecture before code exists.** ADR captures design decision, component docs created with status: provisioned.

**Relationship to c3-orchestrator agent:** This skill uses orchestrator analysis stages but stops after ADR acceptance. No c3-dev execution.

## REQUIRED: Load References

Before proceeding, use Glob to find and Read these files:
1. `**/references/skill-harness.md` - Red flags and complexity rules
2. `**/references/layer-navigation.md` - How to traverse C3 docs
3. `**/references/adr-template.md` - ADR structure
4. `**/references/component-lifecycle.md` - Provisioned status model

## Core Workflow

```
User Request ("provision X", "design X", "plan X")
    ↓
Stage 1: Intent Clarification (Socratic)
    ↓
Stage 2: Current State (analyze existing architecture)
    ↓
Stage 3: Scope Impact (what containers/components affected)
    ↓
Stage 4: Create ADR (status: proposed)
    ↓
Stage 4b: User Accepts ADR
    ↓
Stage 5: Create Provisioned Docs
    ├── New component: .c3/provisioned/c3-X/c3-xxx.md
    └── Update to existing: .c3/provisioned/c3-X/c3-xxx.md (with supersedes:)
    ↓
Stage 6: Update ADR status: provisioned
    ↓
DONE (no execution phase)
```

## Progress Checklist

Copy and track as you work:

```
Provision Progress:
- [ ] Stage 1: Intent clarified (what to provision, why)
- [ ] Stage 2: Current state documented
- [ ] Stage 3: Scope assessed (affected containers/components)
- [ ] Stage 4: ADR created (status: proposed)
- [ ] Stage 4b: ADR accepted by user
- [ ] Stage 5: Provisioned docs created
- [ ] Stage 6: ADR status updated to provisioned
```

---

## Stage 1: Intent

| Step | Action |
|------|--------|
| Analyze | What component/feature? New or update? Why provision vs implement? |
| Ask | Use AskUserQuestion: What problem does this solve? Scope? |
| Synthesize | `Intent: Provision [component] Goal: [outcome] Type: [new/update]` |
| Review | User confirms or corrects |

**Key que