gaia-infra-design

To plan infrastructure architecture and IaC structure, orchestrate end-to-end design by loading architecture data and delegating topology, environment planning, and observability to generate a formal infrastructure design document.

Generating deployment topology and observability plans requires loading existing architecture artifacts, delegating design steps to a DevOps subagent, and writing the final rationale and checkpoints to an infrastructure design document.

Yes, infrastructure design planning requires an existing architecture.md file at docs/planning-artifacts/architecture.md to load topology data and coordinate environment design before generating the final plan.

Yes, this infrastructure design process suits projects requiring formal architecture artifacts, deployment topology, and environment design, ensuring traceable decisions by recording them in memory and emitting lifecycle events.

The final infrastructure design document is saved to docs/planning-artifacts/infrastructure-design.md, containing the deployment topology, IaC module structure, environment design, and rationale for each decision.

The infrastructure design workflow coordinates DevOps guidance by delegating architecture design, environment planning, and observability steps to a devops subagent, recording decisions in memory to ensure a traceable process.