create-architecture

Consolidate GDDs, ADRs, and engine references into a master architecture document.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill create-architecture-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-architecture
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/create-architecture
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill create-architecture-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates fragmented planning and undocumented technical decisions by producing a single, engine-aware master architecture document that maps design requirements to concrete implementation plans and ADR needs.

Core Features & Use Cases

  • Technical requirements extraction: Reads all approved GDDs and the systems index to build a numbered requirements baseline.
  • Engine-aware validation: Loads engine reference docs to flag post-cutoff breaking changes, deprecated APIs, and HIGH/MEDIUM risk domains.
  • Architecture authoring & ADR traceability: Maps systems into layers, defines module ownership, data flows, API boundaries, audits existing ADRs, and lists required new ADRs.
  • Collaborative gating: Supports configurable review modes and coordinates Technical Director sign-off and Lead Programmer feasibility checks.
  • Use Case: Use this Skill before sprint planning to ensure every GDD requirement has an architectural decision and required ADRs are identified.

Quick Start

Run the create-architecture skill in full review mode to generate the master architecture document from existing GDDs, ADRs, and engine references.

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 game architecture blueprint from existing GDDs and ADRs?

To create a game architecture blueprint, consolidate approved Game Design Documents, the systems index, engine references, and existing Architecture Decision Records into a master technical document mapping system layers, data flows, and API boundaries.

When do I need to generate a master architecture document for my game project?

You need a master architecture document during pre-sprint planning and architecture phases to map system layers, define module ownership, specify data flows, and identify required new ADRs before implementation begins.

How to extract technical requirements from game design documents for system architecture planning?

Extract technical requirements by reading all approved GDDs and the systems index to build a numbered requirements baseline, then flag knowledge gaps and trace architectural decisions back to those baseline requirements.

Can I validate engine compatibility and deprecated APIs when planning game system architecture?

Yes, you validate engine compatibility by loading engine reference docs to flag post-cutoff breaking changes, deprecated APIs, and HIGH or MEDIUM risk domains that could impact your system architecture plan.

What's the best way to audit existing ADRs for compatibility with new game system architecture?

The best way to audit ADRs is to review existing Architecture Decision Records alongside engine reference files, checking for compatibility conflicts while mapping systems into layers and identifying any required new ADRs.

Does the architecture document support traceability from game design requirements to technical implementation?

Yes, the architecture document provides traceability by linking the numbered technical requirements baseline extracted from GDDs to specific architectural decisions, module ownership, and required ADRs in the final blueprint.