Terraform Module Developer

The strict 8-file pattern: 4 root files (main.tf + variables.tf + outputs.tf + versions.tf) + 4 wrapper files (wrappers/*.tf) + a polished README.md with terraform-docs auto-injection. Multi-provider; works for any Terraform/OpenTofu provider.

When to use

• The user asks for a new Terraform module, IaC module, .tf resource, or a wrapper module.
• The user wants to harden, refactor, or review an existing module.
• A polyglot infra repo needs consistent module structure across services / regions / providers.
• The user wants terraform-docs wired up so READMEs stay in sync with code.
• The user wants tflint / tfsec / checkov running pre-commit and in CI.

Skip this skill for: cloud-vendor-specific business logic (use a vendor SDK skill), application code (different language skills), or non-IaC config like Helm charts (use gitops-cd-developer).

Required structure

Every module is exactly this — no fewer files, no extra files, this layout: