architecture-review

Validates GDD-to-ADR traceability and detects cross-ADR conflicts.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill architecture-review-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill architecture-review-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates the completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.

Core Features & Use Cases

  • Provides end-to-end architecture quality assurance by validating GDD-to-ADR mappings, ADR dependencies, and engine constraints.
  • Detects coverage gaps, cross-ADR conflicts, and inconsistencies to guide ADR creation and revision.
  • Produces a formal verdict and enables traceability through a documented matrix and reports.
  • Applies to multi-ADR game projects where engine versions and system boundaries must remain coherent.

Quick Start

Invoke the architecture-review skill with focus: full to perform a complete architecture review across all GDDs and ADRs

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I validate alignment between game design documents and architectural decisions?

To validate GDD-to-ADR alignment, build a traceability matrix mapping every technical requirement to specific architectural decisions. This process detects coverage gaps, identifies cross-ADR conflicts, and ensures engine compatibility consistency across your project pipeline.

What is a traceability matrix for multi-ADR game projects?

A traceability matrix for multi-ADR projects maps every game design document technical requirement directly to corresponding architectural decision records. It enforces architecture quality assurance by exposing coverage gaps and detecting conflicting decisions across system boundaries.

How do I detect cross-ADR conflicts and coverage gaps in my architecture?

Detecting cross-ADR conflicts and coverage gaps requires auditing architectural decisions against all game design documents. Applying a standardized ADR framework verifies dependencies, highlights missing mappings, and produces a formal PASS, CONCERNS, or FAIL verdict.

Can I audit engine version compatibility consistency across multiple architectural decisions?

Yes, you can audit engine compatibility consistency by applying a standardized ADR framework across all decisions. This verifies that engine versions and system boundaries remain coherent throughout the design-to-production pipeline.

What is the best way to perform a full architecture review across all GDDs and ADRs?

The best way to perform a full architecture review is to validate GDD-to-ADR mappings, ADR dependencies, and engine constraints simultaneously. This end-to-end quality assurance detects inconsistencies and produces a formal verdict with documented reports.

When do I need an architecture review for my game project?

You need an architecture review when managing multi-ADR game projects where engine versions and system boundaries must remain coherent. It is essential for identifying cross-ADR conflicts, verifying GDD coverage, and guiding architectural decision creation and revision.