!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow

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.

---

Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

workflow (see .claude/docs/workflow-modes.md):

• full, full traceability matrix across all GDDs and all ADRs.
• standard, reduced scope: architecture doc + critical ADRs only.
• minimal, not applicable (no architecture doc required).

Phase 1: Load Everything

Read references/1-load.md now and follow it, this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 2: Extract Technical Requirements from Every GDD

Read references/2-extract-requirements.md now and follow it, this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 3: Build the Traceability Matrix