What problem does it solve? After an infrastructure review identifies deletable AWS resources, teams need a safe, repeatable way to actually destroy them through the owning Terraform or Terragrunt stacks instead of ad-hoc AWS CLI mutations that bypass code ownership and audit trails. ## Core Features & Use Cases - Owning-stack execution only: Runs cleanup exclusively through the repo-owned Terraform or Terragrunt command path, never one-off AWS mutation scripts. - Approval-gated destroys: Requires explicit cleanup approval text before applying, captures destroy plan artifacts, and keeps stack scope narrow. - Safety defaults: Retains shared IAM roles/policies and retain-protected buckets unless explicit delete approval exists, and stops with a blocker when account or environment is unclear. - Use Case: After aws-ec2-ami-cleanup-inventory accepts EC2/EBS/AMI/snapshot cleanup candidates in RESULT.md, use this Skill to execute the approved deletions via the owning Terragrunt stack and record commands, approvals, and residual risk in a new RESULT.md. ## Quick Start Execute the approved cleanup candidates from the review RESULT.md using the owning Terragrunt stack and write the command log and approvals to a new RESULT.md.
