create-architecture

Create a master game architecture document from GDDs, ADRs, and engine context.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill create-architecture-thilthpc01208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-architecture
Source: https://github.com/thilthpc01208/Codex-Game-Studios/tree/main/.codex/skills/create-architecture
Command: npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill create-architecture-thilthpc01208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the end-to-end architecture planning for game projects by integrating GDDs, engine context, ADRs, and governance into a single master document.

Core Features & Use Cases

  • Phase-driven system mapping, data-flow definitions, ADR traceability, and sign-off scaffolding.
  • Engine risk-aware analysis and ADR coverage checks to ensure design decisions align with the pinned engine version.
  • Governance-ready outputs that feed gates, ADRs, and handoffs.

Quick Start

Load the full project context, map systems to layers, define ownership, assess ADR needs, and prepare the master architecture document for sign-off.

Frequently Asked Questions about create-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a master game architecture document from multiple GDDs and ADRs?

Master game architecture planning integrates Game Design Documents, engine context, and Architecture Decision Records into a single document to coordinate phase-by-phase system mapping, data flow, and governance before coding begins.

What is phase-by-phase system mapping for large-scale game projects?

Phase-by-phase system mapping is an architecture activity that defines system layers, ownership, and data flow across game projects, ensuring structured governance and clear API boundaries before implementation starts.

How do I perform an engine risk assessment and ADR audit before coding begins?

Perform an engine risk assessment by evaluating whether your design decisions and Architecture Decision Records align with the pinned engine version, using automated coverage checks to trace gaps before sign-off.

Can I use this architecture planning approach for projects with multiple GDDs and ADRs?

Yes, this architecture planning approach is specifically designed for large-scale game projects with multiple Game Design Documents and Architecture Decision Records, automating cross-cutting requirement integration and phase-based mapping.

What's the best way to prepare architecture documentation for sign-off workflows?

The best way to prepare architecture documentation for sign-off is to generate governance-ready outputs that feed approval gates, track ADR traceability, and define API boundaries for formal handoffs.

Do I need to provide full project context to map systems to layers?

Yes, you need to load the full project context including engine context and cross-cutting requirements to accurately map systems to layers, define ownership, and assess ADR needs for the master document.