azure-enterprise-infra-planner

Describe your workload, traffic, data, and security requirements, and the skill runs a seven-phase workflow: insight extraction, WAF research, resource research, plan generation, verification, IaC generation, and deployment. Each phase has gate conditions requiring your approval before proceeding.

Both are supported and generated from the same approved infrastructure plan. Bicep uses az deployment group or sub create depending on targetScope, while Terraform uses init, plan, and apply with per-environment tfvars files. You choose the flavor explicitly before generation begins.

No. Deployment is a destructive action gated behind explicit user confirmation after risks are presented. The plan status must be approved, IaC must pass az bicep build or terraform validate, and vague replies like continue or go ahead are not accepted.

Reference files cover AI and ML, compute PaaS and IaaS, relational and analytics data services, messaging, monitoring, networking, and security resources. Each category documents ARM types, API versions, CAF naming prefixes, and pairing constraints.

Generation halts if the plan status is not approved, since Phase 6 requires meta.status set to approved after explicit user sign-off in Phase 5. It also stops if you do not clearly name Bicep or Terraform as the desired output.