create-architecture

Generate a master architecture document by synthesizing your GDD, systems index, ADRs, and engine reference library into a single blueprint. The output is a ready-to-publish architecture.md file that guides sprint planning and handoffs.

Align game architecture with a specific engine version by validating your design decisions and systems index against the pinned engine reference library. This flags gaps and version mismatches early, before coding begins, ensuring your architecture document stays accurate.

Consolidate ADRs and GDDs by synthesizing them with the systems index and engine reference data into a master architecture blueprint. This automated process produces a baseline document at docs/architecture/architecture.md to guide ADRs and gate decisions.

You need a master architecture blueprint during end-to-end game architecture planning, from discovery through documentation. It is required when consolidating multiple design documents, validating engine-version alignment, and flagging risks before starting implementation.

Yes, architecture risks are flagged during the blueprint generation process by validating your consolidated GDDs and systems index against the engine reference library. This early risk flagging identifies gaps and misalignments before development starts.

The architecture document generation synthesizes GDDs, the systems index, ADRs, and the engine reference library. While existing ADRs enrich the blueprint, the produced architecture.md serves as a baseline to guide the creation of future ADRs and gate decisions.