architecture-review

Validate GDD technical requirements against ADR architecture decisions.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill architecture-review-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill architecture-review-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents architectural drift by validating that your ADRs fully and consistently implement every technical requirement from your GDDs, while staying aligned with the pinned engine version.

Core Features & Use Cases

  • Completeness validation: Ensures every GDD technical requirement is addressed by at least one ADR and reports PASS/CONCERNS/FAIL.
  • Traceability matrix generation: Produces a traceability matrix (and an RTM mode that extends it with story + test evidence) to quantify coverage gaps.
  • Consistency and conflict detection: Detects cross-ADR conflicts (integration contract, state ownership, dependency order, performance budget issues) and verifies engine compatibility assumptions.
  • Targeted review modes: Supports full review, coverage-only, consistency-only, engine-only, and single-GDD review to narrow scope.
  • Production-ready RTM option: In rtm mode, generates docs/architecture/requirements-traceability.md to link requirements → ADRs → stories → tests.

Quick Start

Run the architecture-review skill in full mode to validate that all GDD requirements are covered by ADRs and that the architecture matches the pinned engine version.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I validate that my game design document technical requirements are fully covered by architecture decisions?

GDD technical requirement coverage is validated by checking that every requirement is addressed by at least one ADR, reporting a structured PASS, CONCERNS, or FAIL verdict to quantify coverage gaps.

What is a requirements traceability matrix for game architecture and how does it link ADRs to tests?

A requirements traceability matrix for game architecture maps GDD requirements to ADRs, and in RTM mode, extends this linkage to include user stories and test evidence for full production traceability.

How do I detect cross-ADR conflicts and integration contract issues in my game engine architecture?

Cross-ADR conflict detection identifies integration contract mismatches, state ownership disputes, dependency order errors, and performance budget issues by verifying consistency across all your architecture decision records.

Can I check engine compatibility assumptions and version consistency across my game architecture documents?

Engine compatibility audits verify that ADRs stay aligned with the pinned engine version, performing consistency checks to ensure technical assumptions match the targeted engine version across all documents.

Does the architecture review support coverage-only or single-GDD focused reviews instead of full production gates?

Targeted review modes support coverage-only gap discovery, consistency-only checks, engine-only audits, and single-GDD focused reviews, allowing you to narrow the validation scope instead of running full production architecture gates.

What is the best way to prevent architectural drift between game design documents and engine version decisions?

Preventing architectural drift requires validating that ADRs fully and consistently implement GDD technical requirements while staying aligned with the pinned engine version, producing a structured verdict output for review gates.