What problem does it solve? Game projects often jump from design documents straight into code, leaving system boundaries, data flows, and engine-version risks undecided until they cause rework. This Skill turns approved GDDs into a complete, reviewed technical blueprint before any code is written. ## Core Features & Use Cases - Guided architecture authoring: Walks through system layer mapping, module ownership, data flow, and API boundaries section by section, writing each approved part incrementally to docs/architecture/architecture.md. - Engine-version awareness: Reads the engine reference library to flag HIGH and MEDIUM risk post-cutoff APIs and validates every engine call against the pinned engine version. - ADR audit and traceability: Builds a Technical Requirements Baseline from all GDDs, audits existing ADRs for coverage gaps, and lists the new ADRs required before coding starts. - Use Case: After approving GDDs for a Godot 4.6 project, run this Skill to produce the master architecture document, get Technical Director and Lead Programmer sign-off, and receive a prioritized list of ADRs to write next. ## Quick Start Ask the AI to run the create-architecture skill to build the master architecture document from the approved GDDs and engine reference for this project.