architecture-review

Validates GDD requirement coverage and cross-ADR consistency with a traceability matrix.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Game projects accumulate design documents (GDDs) and architecture decision records (ADRs) that drift apart, leaving requirements unimplemented, conflicting decisions, and engine-version mismatches discovered only late in production. ## Core Features & Use Cases - Traceability Matrix: Maps every GDD technical requirement to the ADRs that cover it, flagging covered, partial, and gap items with stable TR-IDs persisted in a registry. - Conflict and Engine Audits: Detects cross-ADR contradictions (data ownership, performance budgets, dependency cycles) and checks deprecated APIs, stale engine versions, and post-cutoff API assumptions. - Use Case: Before entering pre-production on a Godot game, run a full review to confirm all combat and inventory GDD requirements have accepted ADRs, then receive a PASS/CONCERNS/FAIL verdict with a prioritized list of ADRs to write. ## Quick Start Ask the AI to run an architecture review over the design/gdd and docs/architecture folders and report the coverage 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 design documents are covered by architecture decisions?

Run the architecture review to extract technical requirements from every GDD and map them to ADRs in a traceability matrix. Each requirement is marked covered, partial, or gap, with suggested ADR titles for uncovered items.

How to detect conflicts between architecture decision records?

The review compares every ADR pair for data ownership, integration contract, performance budget, dependency, pattern, and state management conflicts. It also topologically sorts ADR dependencies and flags unresolved dependencies and cycles.

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

Yes, the engine compatibility audit reads engine reference docs for the project's pinned engine and version. It checks deprecated APIs, stale version references, and post-cutoff API assumptions across all ADRs.

What review modes does the architecture review support?

Modes include full review, coverage-only traceability, consistency-only conflict detection, engine-only audit, single-GDD review, and rtm mode which extends the matrix to story and test file linkage.

What happens when the architecture review finds requirement gaps?

Gaps are listed with suggested ADR titles, domain, and engine risk level, and the verdict becomes CONCERNS or FAIL. The handoff phase prioritizes the top ADRs to create and checks pre-gate items before allowing gate-check.