terraform-validationlisted

## Input - Terraform path or directory (required) - Validation script: `scripts/validate.sh` (required, run from the terraform-validation skill directory) - Optional flags: `--fix`, `--verbose` ## Output Specification Return structured Markdown in accordance with [references/common-output-format.md](references/common-output-format.md). That file is the source of truth for the output contract. Structured results in fixed order: terraform fmt, terraform validate, tflint, trivy config. ## Execution Scope - **Always use `scripts/validate.sh`** for comprehensive validation. Do not run individual commands. - Script runs all checks in deterministic order. - Individual commands are for debugging only (see [references/common-individual-commands.md](references/common-individual-commands.md)). - **Do not review code design decisions** (use terraform-review for that) ### USE FOR: - run Terraform syntax/lint/security checks before commit - reproduce CI validation failures locally - validate a scoped Terraform directory during iterative changes ### DO NOT USE FOR: - perform design and architecture review (use terraform-review) - implement Terraform resource changes as a primary task - validate non-Terraform files ## Reference Files Guide - [common-checklist.md](references/common-checklist.md) (always read) - [common-output-format.md](references/common-output-format.md) (always read) - [common-troubleshooting.md](references/common-troubleshooting.md) (read on failure) - [common-