architecture-review

Map GDD requirements to ADRs and verify engine compatibility.

Updated Apr 15, 2026

Search Tags:#architecture #adr #traceability #game-design #gdd #engine-audit

Ready to run

npx skills add https://github.com/sumilee-pcu/game2026 --skill architecture-review-sumilee-pcu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/sumilee-pcu/game2026/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/sumilee-pcu/game2026 --skill architecture-review-sumilee-pcu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of architectural drift and inconsistency in complex game projects by ensuring that every technical decision aligns with the game design documents and engine constraints.

Core Features & Use Cases

Traceability Mapping: Automatically maps GDD requirements to Architectural Decision Records (ADRs) to identify coverage gaps.
Conflict Detection: Detects cross-ADR contradictions, dependency cycles, and engine compatibility issues.
Engine Audit: Verifies that architectural decisions remain consistent with the project's specific engine version and deprecated API lists.

Quick Start

Run the architecture review skill to perform a full validation of the current project architecture against all design documents.

Frequently Asked Questions about architecture-review

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

FAQPage Schema

How do I validate game architecture against design documents?▼

To validate game architecture, this skill maps GDD requirements to ADRs and engine specifications, detecting cross-system conflicts and verifying engine compatibility to produce a PASS, CONCERNS, or FAIL review verdict.

How do I check traceability between my game design document and architectural decisions?▼

Checking traceability involves mapping GDD requirements directly to Architectural Decision Records, which this skill does automatically to identify coverage gaps where design requirements lack corresponding technical decisions.

Why does my game project have architectural drift and cross-system conflicts?▼

Architectural drift and cross-system conflicts occur when technical decisions contradict each other or violate engine constraints, detectable by analyzing ADR dependencies and verifying engine compatibility against deprecated APIs.

What's the best way to audit engine compatibility for architectural decisions?▼

The best way to audit engine compatibility is to verify all architectural decisions against the project's specific engine version and deprecated API lists, checking for contradictions and dependency cycles across ADRs.

Can I review my project architecture without manually comparing ADRs to the game design document?▼

Yes, you can review project architecture automatically by running a full validation that maps GDD requirements to ADRs, detects cross-ADR contradictions, and produces an actionable implementation order report.

Does architecture review work for complex game projects with multiple conflicting ADRs?▼

Architecture review works for complex game projects by detecting cross-ADR contradictions, dependency cycles, and engine compatibility issues, then generating a comprehensive review with an actionable implementation order.