architecture-decision

When this skill is invoked: ## 0. Parse Arguments — Detect Retrofit Mode Resolve the review mode (once, store for all gate spawns this run): 1. If `--review [full|lean|solo]` was passed → use that 2. Else read `production/review-mode.txt` → use that value 3. Else → default to `lean` See `docs/framework/director-gates.md` for the full check pattern. **If the argument starts with `retrofit` followed by a file path** (e.g., `/architecture-decision retrofit docs/architecture/adr-0001-event-system.md`): Enter **retrofit mode**: 1. Read the existing ADR file completely. 2. Identify which template sections are present by scanning headings: - `## Status` — **BLOCKING if missing**: `/story-readiness` cannot check ADR acceptance - `## ADR Dependencies` — HIGH if missing: dependency ordering breaks - `## Engine Compatibility` — HIGH if missing: post-cutoff risk unknown - `## GDD Requirements Addressed` — MEDIUM if missing: traceability lost 3. Present to the user: ``` ## Retrofit: [ADR title] File: [path] Sections already present (will not be touched): ✓ Status: [current value, or "MISSING — will add"] ✓ [section] Missing sections to add: ✗ Status — BLOCKING (stories cannot validate ADR acceptance without this) ✗ ADR Dependencies — HIGH ✗ Engine Compatibility — HIGH ``` 4. Ask: "Shall I add the [N] missing sections? I will not modify any existing content." 5. If yes: - For **Status**: ask the user — "What is the current status of t...