What problem does it solve? Major technical decisions in game development often go undocumented, leading to inconsistent implementations, contradictory designs, and lost context when team members change. This Skill produces structured Architecture Decision Records (ADRs) that capture the context, alternatives, and consequences of every significant technical choice. ## Core Features & Use Cases - Guided ADR Authoring: Walks through problem framing, alternatives analysis, dependency mapping, and GDD traceability using a standardized ADR template with engine compatibility tables. - Retrofit Mode: Scans existing ADR files for missing sections (Status, ADR Dependencies, Engine Compatibility, GDD Requirements) and appends only the absent sections without modifying existing content. - Registry & Consistency Gates: Checks an architecture registry for conflicting stances, validates drafts with engine specialist and technical director reviews, and detects GDD naming inconsistencies before writing. - Use Case: A team deciding between an event bus and direct signal connections for their Godot project runs this Skill to produce ADR-0003 with verified engine API references, registered interface contracts, and links to the GDD systems it satisfies. ## Quick Start Ask the AI to create an architecture decision record for your technical choice, for example by saying: use the architecture-decision skill to document our event system architecture decision.