terraform

Manage Terraform infrastructure definitions with remote state, locking, and CI/CD plan/apply workflows.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/christopherclemmons/startupkit --skill terraform-christopherclemmons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform
Source: https://github.com/christopherclemmons/startupkit/tree/main/skills/terraform
Command: npx skills add https://github.com/christopherclemmons/startupkit --skill terraform-christopherclemmons

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear, production-ready set of standards and practices to avoid inconsistent, insecure, or unreviewable Terraform changes that cause drift, outages, or unmanaged cloud sprawl. It reduces risk from ad-hoc console edits, missing state locking, poorly versioned modules, and unclear environment separation.

Core Features & Use Cases

  • Standards and Governance: Enforce remote state with locking, naming conventions, tagging, and least-privilege access models.
  • Reusable Modules: Promote focused, versioned modules for VPCs, compute, databases, load balancers, and other common patterns.
  • Safe Workflows: Integrate plan-and-review processes into CI/CD, require manual approvals for production applies, and document rollback paths.
  • Security and Cost Controls: Ensure encryption, private networking for sensitive resources, and cost-aware provisioning and cleanup.
  • Use Case: A platform team uses these standards to create sharable modules and CI pipelines so multiple product teams can provision isolated dev, staging, and prod environments without shared mutable state.

Quick Start

Generate a Terraform module for an S3-compatible storage component with variables for name, environment, encryption enabled, tags for owner and cost center, and a remote state configuration for dev and prod environments.

Frequently Asked Questions about terraform

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

FAQPage Schema
How do I enforce remote state with locking in Terraform CI/CD workflows?

To enforce remote state with locking in Terraform, integrate plan-and-review processes into CI/CD pipelines that require manual approvals for applies. This ensures safe, reproducible infrastructure changes across isolated dev, staging, and prod environments.

What is the best way to manage Terraform modules across multiple cloud environments?

Managing Terraform modules across cloud environments requires focused, versioned modules for common patterns like VPCs and databases. Enforce naming conventions, tagging, and least-privilege IAM to maintain consistent, secure provisioning.

Why does Terraform infrastructure drift occur and how can I prevent it?

Terraform infrastructure drift occurs from ad-hoc console edits and missing state locking. Prevent drift by applying production-ready standards for remote state, module versioning, and continuous drift detection within your provisioning workflows.

Can I use Terraform to provision isolated dev and prod environments from shared modules?

Yes, you can use Terraform to provision isolated dev and prod environments by creating sharable, versioned modules. Platform teams use these standards with CI pipelines to allow product teams to provision without shared mutable state.

How do I generate a secure Terraform module for S3-compatible storage?

To generate a secure Terraform module for S3-compatible storage, define variables for name, environment, and encryption. Include tags for owner and cost center, and configure remote state for separate dev and prod environments.

What are the limitations of ad-hoc Terraform changes in production?

Ad-hoc Terraform changes in production cause outages, unmanaged cloud sprawl, and unreviewable drift. Without remote state locking and least-privilege IAM, manual console edits bypass security controls and rollback documentation.