architecture-review

Validate ADR coverage, traceability, and engine-version alignment in multi-ADR projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill architecture-review-thilthpc01208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/thilthpc01208/Codex-Game-Studios/tree/main/.codex/skills/architecture-review
Command: npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill architecture-review-thilthpc01208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Architecture Review skill ensures that the complete set of design decisions covers all GDD requirements, remains internally consistent, and aligns with the pinned engine version, acting as the quality gate before production planning.

Core Features & Use Cases

  • Builds a traceability matrix mapping GDD requirements to ADRs and decisions to highlight coverage gaps.
  • Detects cross-ADR conflicts, inconsistent interfaces, and engine-version mismatches to prevent misalignment.
  • Produces structured outputs and handoff-ready documentation for architecture reviews, stage gates, and planning sessions.

Quick Start

Run architecture-review to validate ADR coverage, traceability, and engine-alignment for your project.

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 ADRs cover all GDD requirements?

To check ADR coverage for GDD requirements, you need to build a traceability matrix mapping each requirement to its corresponding architecture decision. This process highlights coverage gaps and ensures all design decisions are accounted for before production planning.

How do I detect conflicts across multiple ADRs in a project?

Detecting cross-ADR conflicts requires running consistency checks across your multi-ADR project to identify inconsistent interfaces and misalignment. Automated architecture reviews validate dependencies and surface conflicting decisions to prevent integration issues.

What is architecture traceability and when do I need it?

Architecture traceability is the mapping of design decisions back to original requirements to ensure complete coverage. You need it during architecture reviews and stage gates to validate that every requirement is addressed and dependencies are correctly ordered.

Can I validate engine-version alignment against my architecture decisions?

Yes, you can validate engine-version alignment by applying compatibility checks against your pinned engine version during the architecture review. This detects engine-version mismatches and ensures your ADRs align with the specified engine constraints.

What is the best way to automate architecture reviews for stage gates?

The best way to automate architecture reviews for stage gates is to validate ADR coverage, traceability, and engine alignment in a single pass. This produces structured, handoff-ready documentation required for planning sessions and quality gates.