architecture-review

Validate architectural decisions against GDD requirements and cross-ADR consistency.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill architecture-review-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill architecture-review-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

architecture-review prevents fragile, inconsistent game/AI architecture by checking whether the architecture decisions (ADRs) fully and coherently cover every requirement in the game design documents (GDDs), including engine compatibility.

Core Features & Use Cases

  • Completeness validation (Coverage): Detects which GDD technical requirements have no corresponding ADR coverage.
  • Consistency validation (Conflicts): Finds cross-ADR conflicts, including data ownership, integration contracts, performance budget collisions, dependency cycles, and state authority overlaps.
  • Engine compatibility auditing (Targeting the pinned engine): Verifies that ADRs consistently target the pinned engine version and checks for deprecated API references.

Quick Start

Run architecture-review in full mode to validate completeness, traceability, cross-ADR consistency, and engine compatibility for the entire project.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I validate architecture coverage against game design documents before production?

Architecture coverage validation checks if architectural decisions fully cover every technical requirement in game design documents. It detects uncovered requirements and outputs a PASS, CONCERNS, or FAIL status to gate pre-production readiness.

How do I generate a Requirements Traceability Matrix for single or multiple GDDs?

Requirements Traceability Matrix generation maps extracted technical requirements from game design documents to specific architectural decisions. It builds a single-GDD traceability matrix that validates full requirement mapping and outputs structural coverage gaps.

Can I run an engine compatibility audit to check for deprecated API references in ADRs?

Engine compatibility auditing verifies that architecture decisions consistently target a pinned engine version. It cross-checks engine compatibility by scanning ADRs for deprecated API references and flagging mismatches against the specified engine version.

What is the best way to run a focused consistency-only audit on architectural decisions?

A consistency-only audit focuses exclusively on finding cross-ADR conflicts without running completeness validation. It isolates architectural consistency checking to detect dependency cycles and data ownership overlaps efficiently.

Why does my architecture review return a CONCERNS status instead of PASS?

A CONCERNS status indicates partial coverage or minor inconsistencies between architectural decisions and game design document requirements. It flags unresolved technical requirement gaps, cross-ADR conflicts, or engine compatibility issues that require attention before passing.