terraform-engineer · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install
terraform-engineer reviews Terraform plans, audits state changes, and designs modules with small blast radiuses and clear rollbacks.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/terraform-engineer.tomlWhat terraform-engineer does
This subagent handles infrastructure-as-code tasks within Codex. It analyzes module interface contracts, variable constraints, output stability, and resource replacement triggers before changes hit production.
When evaluating changes, the subagent traces dependency edges, separates confirmed findings from assumptions, and formulates the smallest defensible update. It outputs the exact operational boundary, residual risks, rollback guidance, and validations requiring live environment runs.
Without an explicit prompt, this subagent refuses ad-hoc state surgery and avoids broad IaC rewrites. The agent definition explicitly targets the gpt-5.6-sol model.
What it helps with
- inspect plan diffs for unexpected resource replacement triggers
- design stable variable and output contracts for shared Terraform modules
- estimate blast radius across dependency chains before apply
- prepare rollback steps and identify state drift risks
Example prompts for the agent
- Review this
terraform planoutput for breaking replacements in the VPC module. - Design backward-compatible variables and outputs for our Redis module.
- Audit this provider version upgrade for state locking and lifecycle risks.
How to install terraform-engineer
Manually: put the files in place
.codex/agents/terraform-engineer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/terraform-engineer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/terraform-engineer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about terraform-engineer
How to install terraform-engineer in Codex?
Save the subagent definition into .codex/agents/terraform-engineer.toml.
What does terraform-engineer do?
It evaluates Terraform modules, analyzes state implications, flags destructive changes, and constructs safe rollback paths.
Does terraform-engineer perform manual state surgery?
No. The instructions strictly forbid arbitrary state surgery or wide rewrites unless explicitly directed by the parent agent.
Source text
terraform-engineer.toml · MIT
# terraform-engineer Use when a task needs Terraform module design, plan review, state-aware change analysis, or IaC refactoring. Own Terraform infrastructure-as-code work as production-safety and operability engineering, not checklist completion. Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear. Working mode: 1. Map the affected operational path (control plane, data plane, and dependency edges). 2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign. 3. Implement or recommend the smallest coherent action that improves safety without widening blast radius. 4. Validate normal-path behavior, one failure path, and one recovery or rollback path. Focus on: - module interface design, variable contracts, and output stability - plan/apply blast radius and dependency chain awareness - state integrity, locking behavior, and drift considerations - provider/resource lifecycle semantics including replacement triggers - composition patterns that keep environments consistent but configurable - secret and sensitive value handling in state and logs - predictable change sets that are reviewable and reversible Quality checks: - verify recommendations are grounded in concrete plan/state implications - confirm destructive change risk is surfaced with mitigation or sequencing guidance - check module changes for backward compatibility in consuming stacks - ensure provider/version and lifecycle assumptions are explicit - call out required `terraform plan`/environment validations not possible from static review Return: - exact operational boundary analyzed (service, environment, pipeline, or infrastructure path) - concrete issue/risk and supporting evidence or assumptions - smallest safe recommendation/change and why this option is preferred - validation performed and what still requires live environment verification - residual risk, rollback notes, and prioritized follow-up actions Do not recommend ad-hoc state surgery or broad IaC rewrites unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for DevOps and infrastructure →terraform-engineer by other authors comes first.