skills.rest
johnatas-henrique
johnatas-henriqueCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-review

Validate game project architecture against GDDs and ADRs.

Updated Jul 16, 2026
Search Tags:#game development#architecture review#conflict detection#traceability matrix#engine compatibility#adr validation#gdd coverage
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill architecture-review-johnatas-henrique
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-review
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/architecture-review
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill architecture-review-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams often face costly rework when architectural decisions (ADRs) fail to cover all game design document (GDD) requirements, contain internal conflicts, or are incompatible with the project's pinned engine version. This Skill eliminates that risk by providing a structured, end-to-end architecture review process.

Core Features & Use Cases

  • Full Traceability Matrix: Maps every GDD technical requirement to corresponding ADRs to identify uncovered gaps, with optional extension to link requirements to implementation stories and tests.
  • Cross-ADR Conflict Detection: Identifies contradictions between architectural decisions, including data ownership conflicts, performance budget overallocations, dependency cycles, and inconsistent engine API usage.
  • Engine Compatibility Audit: Verifies all ADRs align with the pinned engine version, flags deprecated API usage, and consults engine specialists to catch nuanced compatibility issues.
  • Clear Verdict & Action Items: Produces a PASS/CONCERNS/FAIL verdict with prioritized lists of missing ADRs, conflict resolutions, and pre-gate checklist items to unblock production.
  • Use Case: For a 90s F1 racing game built with Babylon.js, run this skill after drafting all ADRs to confirm every GDD requirement (e.g. 60fps collision detection for 200 track entities) has architectural coverage, no ADRs conflict over physics thread allocation, and all engine API choices are compatible with the project's pinned Babylon.js version.

Quick Start

Run the architecture-review skill with the argument 'full' to perform a complete audit of all GDDs and ADRs in your game 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 game architecture decisions cover all GDD requirements?▼

To check game architecture coverage against GDD requirements, map every technical requirement to corresponding architecture decision records using a traceability matrix. This process identifies uncovered gaps and ensures all design specifications have matching implementation decisions before production begins.

How do I detect conflicts between architecture decision records in game development?▼

Detect cross-ADR conflicts by analyzing architectural decisions for data ownership contradictions, performance budget overallocations, dependency cycles, and inconsistent engine API usage. This validation produces a conflict report highlighting contradictions between recorded implementation choices.

How do I verify game architecture compatibility with a pinned engine version?▼

Verify engine compatibility by auditing all architecture decision records against the pinned engine version documentation. This check flags deprecated API usage and consults engine reference docs to catch nuanced compatibility issues within the game project.

When should I run an architecture review against my game design documents?▼

Run an architecture review during the transition from technical setup to pre-production after drafting all ADRs. This timing validates GDD coverage, resolves implementation conflicts, and produces a prioritized action list before unblocking production gates.

What is a traceability matrix for game architecture and GDD requirements?▼

A traceability matrix maps every game design document technical requirement to its corresponding architecture decision records. It identifies uncovered gaps where design specifications lack implementation decisions, extending optionally to link requirements directly to stories and tests.

Can I audit architecture decisions for a web game engine like Babylon.js?▼

Yes, you can audit architecture decisions for web game engines like Babylon.js. The review validates that ADRs align with the pinned engine version, confirming engine API choices and performance budgets match project constraints.

Related Skills

Explore More Software Engineering Skills→
MichaelSolatiMichaelSolati

architecture-review

Audit game project architecture against GDDs and engine requirements.

Community
Advanced
wtahwtah

implementation-planning

Generate prioritized action items with unique IDs from specification gaps.

Community
Basic
polsegupolsegu

architecture-review

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

Community
Advanced
akaszubskiakaszubski
32

project-alignment

Validate feature alignment against PROJECT.md goals, scope, and constraints.

Community
Advanced