architecture-review

Architecture validation checks whether your architectural decision records fully cover all technical requirements defined in game design documents, producing a PASS, CONCERNS, or FAIL verdict. It builds a traceability matrix mapping requirements to ADRs and highlights any gaps or partial coverage.

Conflict detection audits cross-ADR conflicts, including dependency ordering and integration contract issues, to ensure architectural decisions remain consistent. It cross-checks decisions against each other and verifies engine compatibility consistency across all records.

A requirements traceability matrix maps GDD technical requirements to ADRs to verify complete architectural coverage. You need it during pre-production architecture quality gating to highlight gaps, and optionally to generate RTM artifacts linking requirements to stories and tests for production.

Yes, you can use focused review modes like engine-only, coverage-only, consistency-only, or single-GDD review. These targeted modes allow you to verify engine compatibility consistency or check individual game design documents without running full project validation.

You can generate an optional requirements-to-stories-to-tests RTM during architecture review by selecting the RTM output mode. This produces artifacts that link GDD technical requirements and ADRs to production stories and tests, extending pre-production traceability into the production phase.

A CONCERNS verdict indicates partial coverage or minor inconsistencies between ADRs and GDD technical requirements. The review outputs detailed reports highlighting gaps, cross-ADR conflicts, dependency ordering issues, or engine compatibility mismatches that prevent a full PASS verdict.