create-terragrunt-stack

Create and extend Terragrunt infrastructure configurations with validation checks.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/omattsson/iac-bootstrap --skill create-terragrunt-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-terragrunt-stack
Source: https://github.com/omattsson/iac-bootstrap/tree/main/examples/azure-terragrunt/.github/skills/create-terragrunt-stack
Command: npx skills add https://github.com/omattsson/iac-bootstrap --skill create-terragrunt-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually writing and maintaining Terragrunt configuration files for infrastructure-as-code workspaces is time-consuming and prone to human error, especially as stacks, components, and environments scale.

Core Features & Use Cases

  • Stack and Component Creation: Add new components to existing Terragrunt stacks or onboard entirely new stacks to environments with standardized, repeatable workflows.
  • Shared Config Management: Generate _envcommon configuration files to reuse module settings across multiple components and environments.
  • Dependency and Validation Handling: Wire component dependencies correctly and run built-in validation checks to catch configuration errors before deployment.
  • Use Case: A DevOps engineer can use this skill to quickly add a new monitoring component to an existing production Terragrunt stack, ensuring all dependencies, version pins, and shared configs are correctly configured without manual file editing.

Quick Start

Use the create-terragrunt-stack skill to add a new networking component to your existing production Terragrunt stack.

Frequently Asked Questions about create-terragrunt-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new component to an existing Terragrunt stack without manual file editing?

To add a new component to a Terragrunt stack, automate the creation and extension of infrastructure configurations to eliminate manual setup errors. This ensures dependencies, version pins, and shared configs are correctly wired for deployment.

How do I generate shared _envcommon configurations for multiple Terragrunt environments?

Generate shared _envcommon configurations to reuse module settings across multiple components and environments. This standardizes infrastructure-as-code workspaces and reduces configuration drift.

Why does my Terragrunt plan fail with dependency mock output errors?

Terragrunt plan failures often stem from incorrect dependency mock outputs. Resolve this by using built-in validation checks that wire component dependencies correctly and verify mock outputs before deployment.

Can I use this approach to onboard entirely new environments or regions to my infrastructure-as-code workspace?

Yes, onboard entirely new stacks to environments or regions with standardized, repeatable workflows. This automates infrastructure configuration creation and enforces validation to reduce deployment risk.

What is the best way to enforce module version pinning in Terragrunt subscription.hcl files?

The best way to enforce module version pinning is through automated validation of subscription.hcl files. This ensures proper module version constraints are maintained across infrastructure-as-code configurations.