architecture-decision

Creates Architecture Decision Records documenting technical decisions, alternatives, and consequences for game projects.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill architecture-decision-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-decision
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/architecture-decision
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill architecture-decision-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Significant technical decisions in game development often go undocumented, leading to inconsistent implementations, lost context, and contradictory architectural choices across systems. This Skill produces structured Architecture Decision Records (ADRs) that capture the decision, its context, alternatives considered, and consequences. ## Core Features & Use Cases - Guided ADR Authoring: Derives assumptions from GDDs, engine reference docs, and existing ADRs, then confirms them with the user before drafting a full ADR with status, dependencies, engine compatibility, and performance implications. - Retrofit Mode: Scans an existing ADR file for missing sections (Status, ADR Dependencies, Engine Compatibility, GDD Requirements Addressed) and appends only the absent sections without modifying existing content. - Registry & Review Integration: Checks the architecture registry for conflicting stances, runs engine-specialist and technical-director validation gates, and updates docs/registry/architecture.yaml with new stances after approval. - Use Case: A team deciding on an event system architecture for a Godot project invokes the skill, which loads engine compatibility data, proposes alternatives, drafts ADR-0004, validates it against registered stances, and writes it to docs/architecture/. ## Quick Start Ask the AI to create an architecture decision record for your event system design using the architecture-decision skill.

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 project?

Invoke the skill with a short decision title, and it loads engine context, derives assumptions from your GDDs and existing ADRs, confirms them with you, then drafts and writes a numbered ADR file to docs/architecture/ after validation.

How do I add missing sections to an existing ADR?

Use retrofit mode by passing 'retrofit' followed by the ADR file path. The skill scans for missing sections like Status, ADR Dependencies, and Engine Compatibility, then appends only the absent sections without modifying existing content.

Does the ADR skill work with Godot and Unity projects?

Yes, it reads engine reference docs under docs/engine-reference/[engine]/ to load version, knowledge-cutoff risk, breaking changes, and deprecated APIs for the configured engine, including Godot, Unity, Unreal, and browser targets.

What happens if my decision conflicts with an existing architectural stance?

The skill checks docs/registry/architecture.yaml before drafting and surfaces conflicts immediately. You can align with the existing stance, supersede the prior ADR explicitly, or document why the case is an exception.

When should I not run architecture review in the same session?

Never run architecture-review in the same session as architecture-decision. The reviewing agent must be independent of the authoring context to give an unbiased assessment, so open a fresh session for review.