What problem does it solve?
This Skill prevents the game “architecture gap” where ideas are documented but the project lacks a concrete, engine-aware plan that coordinates systems, module boundaries, data flow, and ADR traceability.
Core Features & Use Cases
- End-to-end architecture blueprint creation: Builds
docs/architecture/architecture.md by translating approved GDDs and systems inventories into a technical system plan before any sprint coding.
- Engine-version-aware guardrails: Loads the pinned engine reference library to surface HIGH/MEDIUM knowledge gaps, deprecated APIs, and breaking changes so decisions are compatible with the target engine version.
- Structured progression with approvals: Produces a guided walkthrough across layer mapping, module ownership, data flows, API boundaries, ADR audit, required ADR gaps, and master-document writing with user sign-off gates.
- Traceability and ADR integrity checks: Generates a Technical Requirements Baseline and audits existing ADRs for coverage, conflicts, and validity against the pinned engine context.
Quick Start
Create the master game architecture by running /create-architecture --review lean with your current engine configured and your GDDs/design docs already approved.