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.