architecture-review

Validates GDD requirement coverage and cross-ADR consistency in game project architecture.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill architecture-review-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/architecture-review
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill architecture-review-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Game projects accumulate Game Design Documents (GDDs) and Architecture Decision Records (ADRs) that drift apart, leaving technical requirements uncovered, conflicting decisions, and stale engine assumptions. This Skill audits the entire architecture against every GDD and produces a traceability matrix with a PASS/CONCERNS/FAIL verdict before pre-production begins. ## Core Features & Use Cases - Requirements Traceability Matrix: Extracts technical requirements from every GDD, maps each to ADRs with Covered/Partial/Gap status, and maintains a stable TR-ID registry across review runs. - Cross-ADR Conflict Detection: Detects data ownership, integration contract, performance budget, dependency cycle, and state management conflicts between ADRs, plus a topologically sorted implementation order. - Engine Compatibility Audit: Verifies version consistency, deprecated API usage, and post-cutoff API assumptions against pinned engine reference docs, with an optional engine specialist subagent consultation. - Use Case: Before entering pre-production on a Godot game, run the review to discover that the combat GDD's combo-window requirement has no ADR, that two ADRs both claim ownership of the health value, and that one ADR references a deprecated API — then get a prioritized list of ADRs to write. ## Quick Start Ask the AI to run an architecture review over the design/gdd and docs/architecture directories and report the traceability matrix and verdict.

Frequently Asked Questions about architecture-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my game architecture covers all GDD requirements?

Run the architecture review to extract technical requirements from every GDD and build a traceability matrix marking each as Covered, Partial, or Gap against existing ADRs. The report lists each gap with a suggested ADR title and engine risk level.

How to detect conflicts between architecture decision records?

The review compares every ADR pair for data ownership, integration contract, performance budget, dependency cycle, pattern, and state management conflicts. Each conflict is reported with both claims, the impact, and resolution options.

What review modes does the architecture review support?

It supports full review, coverage-only traceability, consistency-only conflict detection, engine-only audit, single-GDD scoped review, and rtm mode which extends the matrix to story files and test files for full requirement-to-test traceability.

Does the architecture review work with Godot, Unity, and Unreal projects?

Yes, it reads the pinned engine name and version from the project's engine reference docs and audits ADRs against that engine's deprecated APIs, breaking changes, and module references. It can also spawn the configured engine specialist subagent for a second opinion.

What does a FAIL verdict mean in an architecture review?

FAIL means critical gaps exist, such as Foundation or Core layer requirements with no ADR, or blocking cross-ADR conflicts. The verdict is advisory; the report lists blocking issues and required ADRs, and the user decides whether to proceed.