iac-discipline

Enforce declarative Infrastructure as Code to prevent infrastructure drift.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/prapanch/agent-coda --skill iac-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iac-discipline
Source: https://github.com/prapanch/agent-coda/tree/main/infra/iac-discipline
Command: npx skills add https://github.com/prapanch/agent-coda --skill iac-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents infrastructure drift by enforcing that cloud resources are created, updated, and reconciled only through version-controlled Infrastructure as Code rather than ad-hoc console changes.

Core Features & Use Cases

  • Declarative IaC over click-ops: Defines desired state and relies on tooling diffs instead of imperative runbooks, reducing re-run breakage.
  • State protection and safe change management: Treats Terraform/Pulumi/stack state as the source of truth with remote state, locking, encryption, and plan-first apply.
  • Team-ready review and drift playbooks: Provides Terraform style guidance, review checklists, and practical detection/resolution steps for drift scenarios.

Quick Start

Use the iac-discipline skill to review your Terraform plan and identify anything that could cause unexpected destroys, drift risk, or unsafe state changes for your deployment.

Frequently Asked Questions about iac-discipline

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

FAQPage Schema
How do I prevent infrastructure drift in Terraform?

Stop Terraform infrastructure drift by standardizing Infrastructure as Code practices that forbid manual console edits and enforce reviewable, declarative changes. Require remote state with locking and encryption, and adopt a plan-first apply discipline to reconcile reality versus declared configuration.

What is infrastructure drift and how does Infrastructure as Code manage it?

Infrastructure drift occurs when cloud resources are changed manually outside of code, causing mismatched state. Infrastructure as Code manages drift by treating declarative configuration and remote state as the source of truth, using plan diffs and detection workflows to reconcile reality with declared state.

How do I review a Terraform plan for unsafe state changes?

Review a Terraform plan for unsafe state changes by applying a safety review checklist that identifies unexpected destroys, drift risk, and unsafe modifications. Follow Terraform style conventions and ensure remote state locking is active before proceeding with the plan-first apply discipline.

Does this Infrastructure as Code discipline work with Pulumi and CloudFormation?

Yes, this Infrastructure as Code discipline applies to Pulumi, CloudFormation, and CDK provisioning. It standardizes state management, plan-first apply discipline, and drift detection workflows across these tools to prevent infrastructure drift and ensure deployment safety.

Why do I need remote state locking for deployment safety?

Remote state locking is required for deployment safety because it prevents concurrent operations from corrupting your state file. Combined with encryption and a plan-first apply discipline, it treats your state as a protected source of truth to safely manage declarative infrastructure changes.