Menu
Use when working with Terraform, Ansible, Pulumi, or any IaC tool — enforces plan-before-apply discipline
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use before any DevOps build, change, or new feature — refine requirements through dialogue before touching infrastructure or code
Use when working with Docker — building images, writing Dockerfiles, debugging container issues
Use to execute a written implementation plan via subagents with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when working with Kubernetes or Helm — authoring, reviewing, hardening, or debugging manifests, Deployments, Services, Ingress, RBAC, NetworkPolicy, or cluster operations
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
| name | infrastructure-provisioning |
| description | Use when working with Terraform, Ansible, Pulumi, or any IaC tool — enforces plan-before-apply discipline |
NEVER APPLY WITHOUT REVIEWING THE PLAN FIRST
Always run terraform plan / ansible --check / pulumi preview and review output before applying.
tooling/iac/. Scaffold, modify, and run commands.# Terraform
terraform init
terraform plan -out=tfplan
# Review tfplan carefully before proceeding
# Ansible
ansible-playbook site.yml --check --diff
# Pulumi
pulumi preview
Look for:
destroy when you expected an update)terraform apply tfplan
# or
pulumi up
terraform show / pulumi stack to confirm stateGeneric modules: tooling/iac/terraform/, tooling/iac/ansible/, tooling/iac/pulumi/
Opinionated starters: tooling/iac/starters/
| Mistake | Prevention |
|---|---|
| Applying without reviewing plan | Always read the plan output fully |
| Local state in production | Use remote state (S3, GCS, Terraform Cloud) |
| Hardcoded values | Use variables and .tfvars files |
| No state locking | Enable state locking (DynamoDB for AWS) |
| Over-privileged IAM roles | Use least-privilege, scope to specific resources |