architecture-decision

Create Architecture Decision Records with required sections for game development projects.

14|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill architecture-decision-euraika-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/architecture-decision
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill architecture-decision-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack a consistent process for documenting significant technical choices, leading to missing context, unclear rationale, and downstream implementation errors.

Core Features & Use Cases

  • Automated ADR scaffolding: Generates a numbered ADR file with required sections such as Status, Engine Compatibility, Dependencies, and GDD linkage.
  • Retrofit mode: Analyzes existing ADR files, identifies missing mandatory sections, and prompts to add them without altering existing content.
  • Engine‑aware validation: Loads engine version data, checks breaking changes, and warns about knowledge gaps before drafting.
  • Architectural registry integration: Proposes new state ownership, interface contracts, and forbidden patterns to be appended to the architecture registry after user approval.
  • Multi‑stage review workflow: Supports review modes (full, lean, solo), engine specialist validation, technical director strategic review, and GDD synchronization checks.

Quick Start

Invoke the architecture-decision skill with a title like “new physics engine selection” to create a full ADR.

Frequently Asked Questions about architecture-decision

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

FAQPage Schema
How do I create an Architecture Decision Record for a game development project?

To create an Architecture Decision Record, provide a title like "new physics engine selection" to generate a numbered file with required sections including Status, Engine Compatibility, Dependencies, and GDD linkage.

What is the best way to document technical decisions and rationale in software architecture?

Documenting technical decisions requires an Architecture Decision Record that captures the choice and its rationale, validates against the architectural registry, and proposes state ownership and interface contract updates.

Can I retrofit existing ADR files to add missing mandatory sections without altering content?

You can retrofit existing ADR files using a retrofit mode that analyzes records, identifies missing mandatory sections, and prompts you to add them without altering existing content.

Does the ADR workflow validate engine compatibility and check for breaking changes?

The ADR workflow validates engine compatibility by loading engine version data, checking breaking changes, and warning about knowledge gaps before drafting the final architecture decision record.

How do I review architecture decisions for engine specialist validation and GDD synchronization?

Review architecture decisions using a multi-stage workflow that supports full, lean, or solo review modes, engine specialist validation, technical director strategic review, and GDD synchronization checks.

When should I not use automated ADR scaffolding for software architecture choices?

Avoid automated ADR scaffolding for minor technical choices that lack significant downstream impact, as the workflow is designed specifically for significant software architecture decisions requiring registry integration.