Design is now approved before any infrastructure code is written (ADR-0005). A new target-architect Specialist produces one graph of Elements, Relationships and Checks; the diagram is rendered from it, deployment guidance must account for every Check, and validation gives a verdict per Check. Requirements, components, products and recommendations carry ids in data files, and a submission with a gap in the Requirements chain is refused. Also in this commit: - Customer cases group Executions, with an intent history per case - lesson candidates are captured when an Execution ends - evaluation gains chain, verdict, judged and interactive checks, and per-case thresholds - Terraform providers are cached between checks - the requirements analyst proposes defaults instead of asking - the legacy-baseline case and the checks that only read it are removed - ADR-0006 (Change requests) accepted; ADR-0004 and ADR-0007 proposed - plans for iterations 4 to 7 under .agents/plans/ Unproven with a real model: no evaluation run has completed on this design. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
44 lines
2.2 KiB
Markdown
44 lines
2.2 KiB
Markdown
---
|
|
name: iac-validation
|
|
description: >-
|
|
Checks Terraform infrastructure-as-code without provisioning anything, using
|
|
the local terraform_fmt, terraform_validate and terraform_plan tools. Use when
|
|
writing deployment guidance or validating it before deployment.
|
|
metadata:
|
|
scope: deployment-guidance validation
|
|
---
|
|
|
|
# IaC validation
|
|
|
|
Every check runs on a scratch copy of the files you pass. Nothing is applied, and no state is written.
|
|
|
|
## Tools
|
|
|
|
- `terraform_fmt(files)`: returns the files formatting changed. Replace your copies with the returned content.
|
|
- `terraform_validate(files)`: runs `init -backend=false` and `validate` offline. It reports syntax errors, unknown references, missing variables and invalid arguments.
|
|
- `terraform_plan(files, variables)`: previews the changes against the live cloud environment. It reads live state, so the first call may pause for the user's permission. Pass every variable the configuration requires.
|
|
|
|
## When writing deployment guidance
|
|
|
|
1. Run `terraform_fmt`, then `terraform_validate`, on the complete set of files you will attach.
|
|
2. Fix every error and run both again, until `terraform_validate` passes.
|
|
3. Attach the formatted files.
|
|
|
|
## When validating deployment guidance
|
|
|
|
1. Run `terraform_validate` on the attached files, and report its verdict and output.
|
|
2. When permission to read the live environment is granted, run `terraform_plan` with the variable values from the requirements, or clearly marked placeholders. Summarise the resources to add, change and destroy, and flag any destroy or replace.
|
|
3. When a check can't run (a missing CLI, a refused permission or a provider download failure), give the user the exact commands to run themselves:
|
|
|
|
```bash
|
|
terraform init -backend=false
|
|
terraform validate
|
|
terraform plan -lock=false -var-file=<your.tfvars>
|
|
```
|
|
|
|
## Reporting verdicts
|
|
|
|
Give a verdict on every Check in the Target architecture and attach them as `verdicts.json`, in the format the requirements-chain Skill gives. The dry-run's result goes in its `dry_run` entry: `pass` when `terraform_validate` passes, `fail` with the error when it does not, and `not_run` when the tool could not run.
|
|
|
|
Never suggest `terraform apply` as part of validation.
|