SkillVaultskills Browse all 1,000+ skills

Performance · Version 1.2.0 · Reviewed 2026-08-02

Terraform Performance Tuning Specialist

Locate and remove the dominant bottleneck in terraform latency attribution and terraform throughput optimization with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Finds the dominant measured bottleneck and designs representative benchmarks for Terraform using configuration, state, provider locks, modules, and saved plans and plan JSON, replacement actions, state drift, and provider diagnostics, with explicit attention to address or immutable-attribute change replacing stateful infrastructure unexpectedly.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Terraform latency attribution
  • Terraform throughput optimization
  • Terraform performance regression guard

How Terraform Performance Tuning Specialist works

You provide

Baseline measurements, workload shape, and the target

It inspects

Dominant cost mechanism behind terraform latency attribution

It decides

A terraform throughput optimization change ranked by impact and risk

You verify

Re-measure under representative load with guardrails

What it checks first

Terraform Performance Tuning Specialist finds the dominant measured bottleneck and designs representative benchmarks for Terraform using configuration, state, provider locks, modules, and saved plans and plan JSON, replacement actions, state drift, and provider diagnostics, with explicit attention to address or immutable-attribute change replacing stateful infrastructure unexpectedly. Use it when the work involves Terraform latency attribution, Terraform throughput optimization, Terraform performance regression guard.

  1. Every resource replacement in the plan, and whether that resource holds state that cannot be recreated.
  2. Address stability across refactors, since re-indexing destroys and recreates unrelated resources.
  3. Whether the executing principal has broader permissions than the change requires.
  4. Provider version pinning, because an unpinned upgrade introduces unrequested plan changes.
  5. Whether secrets appear in state, which is stored in plaintext regardless of the sensitive marker.

Failure modes it recognizes

  • An immutable attribute change silently forcing replacement of a database or stateful volume.
  • Moving resources between modules without move blocks, causing destroy-and-recreate.
  • A data source resolving at plan time to a value that changes before apply, producing inconsistency.
  • State lock held by a crashed run, blocking every subsequent apply until manually cleared.
  • A count-to-for_each conversion re-creating every resource because addresses changed.
  • Drift silenced with ignore_changes, which permanently disables reconciliation for that path.

Answers it will reject

  • Approving from the plan summary counts instead of reading every replacement line.
  • Using targeted applies to work around a broken dependency graph, leaving state partially applied.
  • Committing state files to version control, exposing secrets and creating infrastructure merge conflicts.
  • Granting the pipeline administrative rights so that any plan will succeed.

Decision rules it applies

  • Any replacement of a stateful resource requires a tested backup and restore path before approval.
  • Prefer move blocks over destroy-and-recreate for refactors; they preserve state and cost nothing.
  • Pin provider versions and upgrade deliberately so plan noise is attributable to intent.
  • If the plan cannot be explained line by line, it has not been reviewed.

Evidence it asks for

  • Export the plan as JSON and programmatically list every replace action.
  • Cross-check each replacement against an inventory of stateful resources.
  • Rehearse the change in a non-production environment carrying representative state.

The method inside

  1. Extract decisions, facts, and unresolved questions needed for terraform latency attribution.
  2. Organize terraform throughput optimization around the reader's next decision or action rather than the source order.
  3. Draft terraform performance regression guard with source traceability and no invented behavior.
  4. Run a completeness, consistency, audience, and actionability review before returning the artifact.

Deliverables

  • Terraform latency attribution assessment
  • Terraform throughput optimization decision and action plan
  • Terraform performance regression guard verification checklist

Evidence requirements

  • Profiles, traces, timings, resource metrics, and workload shape
  • Baseline and target percentile
  • Environment, concurrency, and payload details

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the performance tuning specialist to our Terraform system before the next production change. We can provide configuration, state, provider locks, modules, and saved plans; the main concern is address or immutable-attribute change replacing stateful infrastructure unexpectedly.

Expected output

Define the failing percentile and workload, then attribute time with plan JSON, replacement actions, state drift, and provider diagnostics. The likely mechanism to disprove first is address or immutable-attribute change replacing stateful infrastructure unexpectedly. Change one constraint at a time and compare resource use, tail latency, and correctness against a pinned baseline.

Boundaries and compatibility

Ideal for

  • Terraform latency attribution: produce a decision or artifact grounded in supplied evidence.
  • Terraform throughput optimization: produce a decision or artifact grounded in supplied evidence.
  • Terraform performance regression guard: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Optimizing without a baseline
  • Using averages where tail latency determines experience

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.