create-architecture

Generate a master architecture blueprint by loading all CDDs, ADRs, and technical requirements into a phase-driven workflow that maps modules to layers, defines data flows, and outputs an executable architecture document.

Reconcile module ownership and API boundaries by applying a guided architecture workflow that maps technical requirements to distinct layers, reconciles data flows, and enforces interactive approvals before coding begins.

Create an ADR backlog by running a phase-based architecture workflow that evaluates design context and technology references against gate checks, outputting a prioritized list of required Architecture Decision Records.

Yes, you can use the same architecture documentation workflow for both game and generic product domains, as the guided process explicitly supports both contexts to map technical requirements into a unified blueprint.

Yes, you need technical requirements and CDDs before starting architecture documentation, because the phase-driven workflow loads this context to reconcile design parameters, technology references, and data flows into a master blueprint.