architecture-review

# Architecture Review The architecture review validates that the complete body of architectural decisions covers all game design requirements, is internally consistent, and correctly targets the project's pinned engine version. It is the quality gate between Technical Setup and Pre-Production. **Argument modes:** - **No argument / `full`**: Full review — all phases - **`coverage`**: Traceability only — which GDD requirements have no ADR - **`consistency`**: Cross-ADR conflict detection only - **`engine`**: Engine compatibility audit only - **`single-gdd [path]`**: Review architecture coverage for one specific GDD - **`rtm`**: Requirements Traceability Matrix — extends the standard matrix to include story file paths and test file paths; outputs `docs/architecture/requirements-traceability.md` with the full GDD requirement → ADR → Story → Test chain. Use in Production phase when stories and tests exist. --- ## Phase 1: Load Everything ### Phase 1a — L0: Summary Scan (fast, low tokens) Before reading any full document, use Grep to extract `## Summary` sections from all GDDs and ADRs: ``` Grep pattern="## Summary" glob="design/gdd/*.md" output_mode="content" -A 4 Grep pattern="## Summary" glob="docs/architecture/adr-*.md" output_mode="content" -A 3 ``` For `single-gdd [path]` mode: use the target GDD's summary to identify which ADRs reference the same system (Grep ADRs for the system name), then full-read only those ADRs. Skip full-reading unrelated GDDs entirely....