architecture-review

Validate project architecture alignment with GDD technical requirements via traceability and consistency checks.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill architecture-review-easonlao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/easonlao/jiazi-game --skill architecture-review-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from discovering late that architectural decisions don’t fully cover GDD requirements, have contradictions across ADRs, or target an incompatible engine reality.

Core Features & Use Cases

  • GDD → ADR traceability: Builds a requirements-to-architecture traceability matrix, flagging uncovered or partially covered technical requirements.
  • Cross-ADR conflict detection: Detects contradictions such as data ownership conflicts, integration contract mismatches, dependency cycles, and state-management conflicts.
  • Engine compatibility audits: Checks that ADRs align with the pinned engine version and that no deprecated or inconsistent APIs are referenced.
  • Optional RTM mode: Produces an expanded Requirements Traceability Matrix that includes stories and automated test evidence when present.

Quick Start

Run the architecture review in full mode for the project to generate a PASS/CONCERNS/FAIL verdict and coverage gaps report.

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 architecture decisions cover all GDD technical requirements?

Cross-ADR conflict detection identifies contradictions across architecture decision records by checking for data ownership conflicts, integration contract mismatches, dependency cycles, and state-management conflicts. This consistency checking ensures ADR documentation sets remain logically aligned during pre-production quality gates.

Can I validate engine version compatibility against my architecture decision records?

Engine compatibility audits inspect ADRs against pinned engine reference materials to detect deprecated or inconsistent API references. This pre-production gate validates that your architectural decisions align with the actual engine reality and outputs a structured verdict with detected conflicts.

What is a GDD-to-ADR traceability matrix in architecture review?

A GDD-to-ADR traceability matrix maps game design document technical requirements to architecture decision records to identify coverage gaps. This requirements traceability process flags uncovered requirements and generates a structured PASS, CONCERNS, or FAIL verdict for pre-production quality gates.

How do I detect contradictions across architecture decision records?

Cross-ADR consistency checking identifies contradictions across architecture decision records by detecting data ownership conflicts, integration contract mismatches, dependency cycles, and state-management conflicts. This architecture review outputs a structured verdict highlighting these specific contradictions for remediation.

Does architecture review generate a Requirements Traceability Matrix with test evidence?

Yes, the optional RTM mode produces an expanded Requirements Traceability Matrix that includes stories and automated test evidence when present. This supplements the standard GDD-to-ADR traceability matrix to provide deeper coverage validation for pre-production quality gates.

When should I run an architecture review for pre-production quality gates?

Run an architecture review at pre-production quality gates to verify complete project architecture alignment before production begins. This prevents teams from discovering late that architectural decisions have contradictions, target incompatible engine versions, or fail to fully cover GDD technical requirements.