Terraform Stacks

Writes Terraform Stacks configurations for HCP Terraform: components in .tfcomponent.hcl, deployments in .tfdeploy.hcl, OIDC identity tokens, auto-approve rules, linked Stacks and API monitoring. Use when building or debugging a Stack.

DevOpsPack: HashiCorp skillslinkterraform-stacks
Author
Source
hashicorp/agent-skills/plugins/terraform/skills/terraform-stacks @ 5e30fa5
License
MPL-2.0

About this skill

What it does

The skill covers the Terraform Stacks language, a configuration layer above modules that HCP Terraform runs. A Stack is components (each wraps a module from a local path, a registry or git) and deployments (one set of inputs per environment, region or account, 1 to 20 per Stack). It spells out what differs from plain Terraform: files are .tfcomponent.hcl and .tfdeploy.hcl at the repository root, variables need a type and take no validation, provider blocks carry the alias in the header, a config block and for_each, outputs need a type, and modules used as components may not contain provider blocks.

On the deployment side it covers identity_token for OIDC (its preferred way to authenticate), store "varset" for HCP variable sets, deployment_group and deployment_auto_approve rules (Premium tier; orchestrate is deprecated), and publish_output with upstream_input to link Stacks. The CLI needs Terraform 1.13 or later, pinned in a .terraform-version file: terraform stacks init, validate, fmt, then configuration upload, which starts deployment runs; there is no plan or apply. Removing a deployment takes destroy = true, an upload and an approval.

Six files sit in references/: component-blocks.md and deployment-blocks.md list every block and argument, linked-stacks.md covers cross-Stack outputs, examples.md has complete multi-region, multi-cloud and linked Stacks, troubleshooting.md covers common errors, and api-monitoring.md polls the HCP Terraform API with curl and jq, since the CLI watch commands never return and hang automation. It needs an HCP Terraform API token from ~/.terraform.d/credentials.tfrc.json or an environment variable.

When to use it, and when not

Use it to write or fix Stack configurations, roll modules out to several environments and regions, or follow deployment runs.

Without HCP Terraform it has nothing to run on; an ordinary root module needs the style guide.

How to run it

We do not copy this skill: its files are under MPL-2.0, a file-level copyleft licence outside the set we copy under. Install it from HashiCorp's repository with the button to the source: one skill via npx skills add hashicorp/agent-skills/plugins/terraform/skills/terraform-stacks, or the whole terraform plugin, in Claude Code claude plugin marketplace add hashicorp/agent-skills and claude plugin install terraform@hashicorp. In Codex: codex plugin marketplace add hashicorp/agent-skills, then install terraform from /plugins and start a new session. In Claude Code, the plugin's skill may appear as /terraform:terraform-stacks.

  • Claude Code: /terraform-stacks, or ask for the skill by name.
  • Codex: $terraform-stacks.
  • Cursor: type / in the Agent chat and pick terraform-stacks.

Example: /terraform-stacks Turn modules/vpc and modules/app into a Stack with dev and prod deployments in two AWS regions, authenticated with OIDC.

How it differs from similar skills

Nothing outside this pack covers Stacks. Terraform style guide sets conventions for regular HCL, and several of them do not carry over: Stack variables cannot have validation and providers are written differently. Refactor Terraform into modules produces the modules that Stack components then wrap.

Install

This skill is not copied to the catalog: its licence allows a copy only under the same licence, and the catalog does not copy under such licences. Install it from the author's repository.

Open the source

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack HashiCorp skills

Terraform style guide

Applies HashiCorp's Terraform style conventions: standard file split, formatting, naming, typed variables, for_each over count, pinned versions and secrets kept out of state. Use when writing, reviewing or generating Terraform HCL.

Terraform tests

Writes and runs Terraform's native tests in .tftest.hcl files: run blocks, assertions, plan and apply modes, expect_failures, mock providers and CI pipelines. Use when adding tests to a Terraform module or fixing a failing terraform test.

Refactor Terraform into modules

Splits a monolithic Terraform configuration into a reusable module with a typed interface, then migrates state with moved blocks or terraform state mv so nothing is recreated. Use when a root config has grown too large or repeats itself.

Terraform search and import

Finds existing cloud resources with Terraform Search queries in .tfquery.hcl, generates resource and import blocks, and falls back to manual import for unsupported types. Use when bringing hand-made infrastructure under Terraform.

Terraform policy files

Writes, converts and tests HCP Terraform policy files (.policy.hcl, .policytest.hcl), including Sentinel-to-tfpolicy conversion with a quality label per policy. Use when writing a new policy, porting Sentinel or debugging a policy test.

Azure Verified Modules for Terraform

Applies the 37 Azure Verified Modules requirements to Terraform modules: provider versions, sources, naming, variables, outputs, breaking changes and repository rules. Use when writing or reviewing an Azure module meant for AVM certification.

Terraform provider resources

Guides writing Terraform provider resources and data sources on the Plugin Framework: schema, CRUD, not-found handling, import, waiters for eventually consistent APIs and minimum tests. Use when adding, changing or reviewing a provider resource.

Terraform provider test patterns

Covers acceptance tests for Terraform providers with terraform-plugin-testing: test steps, state and plan checks, import, disappears and regression tests, sweepers and ephemeral resources. Use when writing, reviewing or debugging provider acceptance tests.

AWS AMIs with Packer

Builds Amazon Machine Images with Packer's amazon-ebs builder from a ready HCL template, with source filters, multi-region copies, credentials and fixes for common build errors. Use when creating a custom AMI for EC2.