architecture-review

To validate game architecture against GDD requirements, extract technical requirements from design documents and map them to ADRs, generating a traceability matrix that highlights coverage gaps and ensures completeness before production.

Detect cross-ADR conflicts during pre-production by analyzing architecture decisions for contradictory logic, dependency cycles, and performance budget clashes, producing a conflict report to resolve inconsistencies early.

An architecture traceability matrix for game development maps each GDD requirement to corresponding ADRs, stories, and tests, ensuring all design specifications are covered and identifying gaps in technical documentation.

Audit engine compatibility for deprecated APIs by verifying version consistency across architecture decisions and checking for post-cutoff API assumptions, ensuring the project aligns with the chosen engine's technical standards.

Yes, you can use architecture review to pass a technical quality gate by executing a full review that outputs a PASS, CONCERNS, or FAIL verdict with actionable recommendations for ADR creation and GDD revisions.

Mapping GDD requirements to ADRs requires complete design documents and established engine references; without structured pre-production inputs, the traceability matrix cannot accurately detect coverage gaps or cross-ADR conflicts.