create-architecture

Generate a master game architecture document from approved GDDs and ADRs.

72|7|Updated Apr 29, 2026

Search Tags:#architecture #data flow #system design #gdd #api boundaries #adr audit #engine versioning

Ready to run

npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill create-architecture-striderza

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-architecture
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/create-architecture
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill create-architecture-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork of translating multiple GDDs into a coherent, engine-aware architecture by producing a master blueprint that can be used before any sprint coding begins.

Core Features & Use Cases

Guided, section-by-section architecture authoring: Builds docs/architecture/architecture.md by pulling requirements from the full set of approved GDDs and existing architecture/ADR context.
Engine-version-aware validation and risk flagging: Reads the configured engine reference library (version, breaking changes, deprecated APIs, best practices) and highlights knowledge gaps before decisions propagate.
Architecture governance and decision readiness: Generates system layer mappings, ownership maps, data-flow documentation, API boundary contracts, and then audits ADRs for coverage and engine compatibility gaps to identify required new ADRs.

Quick Start

Use the create-architecture skill to generate the full master architecture document for the current project with --review lean.

Frequently Asked Questions about create-architecture

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

FAQPage Schema

How do I translate a Game Design Document into a technical architecture blueprint?▼

To translate a Game Design Document into a technical architecture blueprint, extract a Technical Requirements Baseline from approved GDDs to define system layers, module ownership, data flows, and API boundary contracts.

What is engine version risk flagging in system design?▼

Engine version risk flagging in system design reads the configured engine reference library to identify breaking changes, deprecated APIs, and knowledge gaps, highlighting HIGH or MEDIUM engine risk domains before architecture decisions propagate.

How do I audit Architecture Decision Records for system design coverage?▼

Audit Architecture Decision Records for system design coverage by generating system layer mappings and API boundary contracts, then cross-referencing existing ADRs to produce a traceable list of required new ADRs.

When do I need to define API boundary contracts for game architecture?▼

You need to define API boundary contracts for game architecture during pre-sprint design-to-production workflows to establish clear module ownership and data-flow definitions before any sprint coding begins.

Can I generate a master game architecture document from multiple approved GDDs?▼

Yes, you can generate a master game architecture document from multiple approved GDDs by pulling requirements and existing architecture context to author the blueprint section-by-section, writing the output to docs/architecture/architecture.md.

What are the limitations of relying solely on GDDs for system layering and module ownership?▼

Relying solely on GDDs for system layering and module ownership lacks engine-aware validation and ADR traceability, risking architecture decisions that fail to account for engine version breaking changes or deprecated APIs.