create-architecture

# Create Architecture This skill produces `docs/architecture/architecture.md` — the master architecture document that translates all approved GDDs into a concrete technical blueprint. It sits between design and implementation, and must exist before sprint planning begins. **Distinct from `/architecture-decision`**: ADRs record individual point decisions. This skill creates the whole-system blueprint that gives ADRs their context. 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. **Argument modes:** - **No argument / `full`**: Full guided walkthrough — all sections, start to finish - **`layers`**: Focus on the system layer diagram only - **`data-flow`**: Focus on data flow between modules only - **`api-boundaries`**: Focus on API boundary definitions only - **`adr-audit`**: Audit existing ADRs for engine compatibility gaps only --- ## Phase 0: Load All Context Before anything else, load the full project context in this order: ### 0a. Engine Context (Critical) Read the engine reference library completely: 1. `docs/engine-reference/[engine]/VERSION.md` → Extract: engine name, version, LLM cutoff, post-cutoff risk levels 2. `docs/engine-reference/[engine]/breaking-changes.md` → Extract: all HIGH and MEDIUM risk changes 3. `docs/engine-refe...