← ClaudeAtlas

explain-planlisted

Explain a Terraform plan in plain language that cuts straight to what matters - verdict first, then what changes, then what could hurt. Use this whenever the user pastes or points at plan output (`terraform show -json plan.out`, a plan JSON export, or a plan file that can be rendered that way) and wants to know what it will do, whether it is safe to apply, what will be destroyed or replaced, or a summary for a reviewer or non-Terraform stakeholder. Trigger even when they just say "what does this do", "is this safe", "summarize this plan", or "tl;dr this" with a plan in front of them. Do not use for writing or refactoring Terraform code, state surgery, or provider errors that are not plan output.
rhawk117/cc-terraform-harness · ★ 1 · AI & Automation · score 70
Install: claude install-skill rhawk117/cc-terraform-harness
# Terraform plan explainer A plan is the only honest preview of what `apply` will do, and almost nobody reads the whole thing. Reviewers skim for the `Plan:` line, miss the one `# forces replacement` buried in 400 lines of tag diffs, and find out about the database rebuild during the maintenance window. This skill exists to make the one paragraph that matters impossible to miss. The reader might be the SRE approving the apply, the engineer who wrote the change, or a manager who has never seen HCL. Write so the first two lines serve all three and the rest rewards whoever keeps reading. ## Workflow 1. Get the plan as JSON in a file inside the project root. `plan_digest` reads only `terraform show -json` output and refuses any path outside the project root, so a file under `/tmp` cannot be digested. If the user has a binary plan file (`plan.out`, `tfplan`), render it with `terraform show -json plan.out > plan.json` in the module directory. If they pasted JSON, write it to a file in the project. Plan text is not supported: when that is all you have, ask for the plan file or the JSON rendering, and do not guess values from text. 2. Call the `plan_digest` tool with `path` set to the JSON file. It does the counting so you don't miscount by eye. The result carries `counts` per action, every changed resource in `resource_changes` with its `actions`, the attributes that forced a replacement (`forced_by`), the names of its `sensitive_attributes` and its `flags`, the `output_cha