architecture-review

To build a requirements traceability matrix, cross-reference your Game Design Documents with Architectural Decision Records, stories, and tests. This cross-referencing validates architectural coverage against design requirements to detect gaps and ensure internal consistency.

Detecting cross-ADR conflicts and engine-version inconsistencies requires applying a multi-phase analysis to your architecture. This process validates ADR alignment with your project's pinned engine version to prevent late-stage integration failures and coverage gaps.

Generate a governance-ready architecture review report by validating design coverage and producing formal documentation. The report includes an ADR dependency ordering, conflict detection notes, risk assessments, and a structured remediation plan for identified gaps.

You can validate architectural coverage without external dependencies by running a self-contained multi-phase analysis. The process builds a traceability matrix directly from your existing GDDs and ADRs to identify coverage gaps and internal consistency issues.

An ADR dependency ordering and remediation plan is needed when architectural decisions lack traceability or contain conflicts. It provides governance-ready risk notes and structured steps to resolve coverage gaps and engine-version inconsistencies across your project.