Terraform Module and Repository Scaffold

When to use

Invoke when starting a new Terraform repository, standardizing an existing one's layout, splitting a monolithic configuration into modules, or auditing module/repo structure and review rules before scaling the team or environments.

Do not use for: remote state and secret handling (use terraform-state-and-secret-management), pre-merge plan/policy gates (use terraform-plan-gate-and-policy-as-code), apply/promotion mechanics (use terraform-apply-and-promotion-mechanics), or module registry/versioning/supply chain (use terraform-module-reuse-and-supply-chain).

Inputs

Required:

• Approved infrastructure-platform.md declaring the environment ladder, module boundaries, blast-radius tiers, and target cloud(s).
• Approved architecture/operations decisions on review/ownership posture and promotion-gate expectations (consumed for code-owner rules; gate mechanics are downstream).

Optional: