skills.rest
polsegu
polseguCOMMUNITY
Explore all skills by this author →
Website𝕏@Polsegu11GitHub

architecture-review

Validate architecture completeness and consistency across game design documents and ADRs.

Updated Apr 10, 2026
Search Tags:#adr#traceability#architecture-review#gdd#conflict-detection#engine-audit
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill architecture-review-polsegu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/architecture-review
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill architecture-review-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures the project's architecture fully implements the technical requirements expressed in Game Design Documents and that Architectural Decision Records are complete, consistent, and targeted to the project's pinned engine version. It surfaces missing ADRs, ambiguous or conflicting decisions, engine incompatibilities, and gaps in the implementation lifecycle so the team can prioritize foundational fixes before production.

Core Features & Use Cases

  • Traceability Matrix: Extracts technical requirements from GDDs, reuses or assigns stable TR-IDs, and maps each requirement to ADRs (and optionally to stories and tests) to reveal coverage, partial coverage, and gaps.
  • Conflict & Dependency Analysis: Detects cross-ADR contradictions (data ownership, interfaces, performance budgets, cycles) and produces a topologically sorted ADR implementation order with unresolved-dependency flags.
  • Engine Audit & Design Flags: Verifies engine version consistency, deprecated and post-cutoff API usage, and generates GDD revision flags when design assumptions conflict with verified engine behavior.
  • Outputs & Workflow: Produces a detailed Architecture Review Report, optional Requirements Traceability Matrix (RTM), and can update the TR registry and session state after user approval; suitable for pre-production gate checks and ongoing architectural hygiene.

Quick Start

Run the architecture-review skill in full mode to load GDDs and ADRs, build a requirements traceability matrix, detect conflicts and dependency cycles, audit engine compatibility, and produce a prioritized architecture review report.

Frequently Asked Questions about architecture-review

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

FAQPage Schema
How do I trace game design document requirements to architectural decision records?▼

To trace game design document requirements to architectural decision records, you need a requirements traceability matrix that extracts technical requirements, assigns stable TR-IDs, and maps each requirement to ADRs to reveal coverage, partial coverage, and gaps in your game development repository.

What is the best way to detect cross-ADR conflicts and dependency cycles in a game architecture?▼

The best way to detect cross-ADR conflicts and dependency cycles is to analyze architectural decision records for contradictions in data ownership, interfaces, and performance budgets, then produce a topologically sorted implementation order with unresolved-dependency flags.

How do I audit deprecated engine APIs and verify engine version compatibility for my game project?▼

To audit deprecated engine APIs and verify engine version compatibility, you check the pinned engine version against reference files, flag deprecated and post-cutoff API usage, and generate GDD revision flags when design assumptions conflict with verified engine behavior.

Can I run a targeted architecture consistency audit on a single game design document?▼

Yes, you can run a targeted architecture consistency audit on a single game design document using single-gdd mode, which focuses validation on one GDD and its related ADRs instead of scanning the entire repository in full mode.

When should I run an architecture review for my game development project?▼

You should run an architecture review as a pre-production gate check and for ongoing architectural hygiene, ensuring architectural decision records fully implement GDD technical requirements and match the pinned engine version before production.

What outputs do I get from an architecture review of game design documents and ADRs?▼

From an architecture review of game design documents and ADRs, you get a detailed Architecture Review Report, an optional Requirements Traceability Matrix, and updates to the TR registry and session state after user approval.

Related Skills

Explore More Software Engineering Skills→
johnatas-henriquejohnatas-henrique

architecture-decision

Document technical decisions as standardized Architecture Decision Records for Babylon.js projects.

Community
Advanced
scomofoscomofo

architecture-review

Validate architecture decisions against GDD requirements and engine compatibility.

Community
Advanced
johnatas-henriquejohnatas-henrique

create-stories

Decompose game development epics into traceable stories with TR-IDs and acceptance criteria.

Community
Advanced
FrancisVargaFrancisVarga

architecture-review

Validate GDD technical requirements against ADR architecture decisions.

Community
Advanced