create-architecture

This skill synthesizes approved Game Design Documents and Architecture Decision Records into a master architecture blueprint. It produces a comprehensive architecture.md file that defines system layers, ownership, data flows, and API boundaries adaptable to phase approvals.

To pass engine compatibility checks, the architecture documentation must include engine version pinning and reference engine-specific constraints. This skill satisfies these checks by synthesizing engine references into the architectural scaffold and producing compliant configs and risk assessments.

Yes, you can use phase-based gating to align design and implementation. The master architecture blueprint supports multiple review modes and adapts to phase approvals, ensuring milestone baselines and ADR traceability are met before proceeding to the next project phase.

The best way to structure system layers and API boundaries is by synthesizing GDDs and ADRs into a definitive architectural scaffold. This approach coordinates work across teams by defining ownership and data flows, producing configs and risk assessments for planners and engineers.

Yes, this architecture planning approach produces ADR traceability and risk assessments. By synthesizing approved ADRs and engine references, it generates configs and architecture docs that satisfy milestone baselines and provide comprehensive risk evaluations for the project.

You need to synthesize ADRs and engine references to create a single, engine-aware blueprint that guides implementation. This resolves fragmentation by combining design decisions and technical constraints into one architecture document, ensuring coordinated work across teams.