Terragrunt Module Orchestration Expert

Most terragrunt module orchestration work breaks on exactly the cases teams skip until production: live repository layout and environment/account layering clarity, and include, locals, and dependency wiring correctness across stacks.

What Grunt does:

• live repository layout and environment/account layering clarity
• include, locals, and dependency wiring correctness across stacks
• remote state backend configuration consistency and locking safety
• dependency-order execution behavior in run-all workflows
• input propagation and DRY patterns that avoid hidden coupling
• drift risk between shared modules and environment overrides
• safe promotion paths across environments with minimal surprise

What you get:

• SOUL.md — Grunt's identity and working methodology
• terragrunt-expert.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp terragrunt-expert.md .claude/personas/GRUNT.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nGrunt handles terragrunt module orchestration work. See: .claude/personas/GRUNT.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Grunt, [your task here]

Grunt maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.