agentleFS
itentialitential/infra-agent-skills/skills/infrastructure-plan-execution/SKILL.md

infrastructure-plan-execution

Skill1 starsChanged 32 days agoApache-2.0View on GitHub

Prepare, review, and apply a declarative infrastructure plan, or plan its removal, then inspect the resulting recorded state and outputs and adopt an existing resource under management. Use when a configuration directory must be initialized, validated, planned, applied, or destroyed through a reviewed saved plan. Covers HashiCorp Terraform CLI. Assumes the CLI, an existing configuration, state backend access, and provider credentials are already available; this skill does not install tools or author configuration. Does not cover writing resource definitions, provider-specific resource design, or approval workflows.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not for writing or redesigning the configuration, installing the tool, or managing credentials.

    line 17
  2. Distinctive:

    No wire-level standard governs this capability.

    line 25
  3. Very specific:

    Follow references/<platform>/procedure.md exactly, including its confirmation gates.

    line 30
  4. Distinctive:

    Does not author configuration, choose providers, or design resources.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Infrastructure Plan Execution

Prepares a configuration, produces a reviewed plan, applies or destroys exactly that plan, and reads back recorded state, using the platform's own documented procedure and result vocabulary.

When to use this skill

  • A configuration directory must be initialized or validated before a change.
  • A plan must be produced, reviewed, and then applied, or a removal plan produced and executed.
  • Recorded resource addresses or outputs must be listed.
  • An existing remote object must be bound to a resource address in the configuration.
  • Not for writing or redesigning the configuration, installing the tool, or managing credentials.

Universal concepts (apply regardless of platform)

  • A plan describes proposed changes and is separate from applying it; applying can change or delete real resources.
  • Where a platform documents a saved plan, applying that exact artifact is the reviewed path, and a failed or unreviewed plan is not eligible.
  • Where documented, a failed apply is not rolled back automatically, so a failure can leave the infrastructure partially changed.
  • Where documented, plan artifacts and state can hold sensitive values that terminal output hides.
  • No wire-level standard governs this capability; claims here are hedged accordingly.

Procedure

  1. Identify the platform from the request or the platform argument. If it is not in references/INDEX.md, stop; do not improvise a procedure.
  2. Follow references/<platform>/procedure.md exactly, including its confirmation gates.
  3. Report the outcome in that procedure's own result vocabulary, preserving partial or incomplete results.

Known limitations

  • Does not author configuration, choose providers, or design resources.
  • Platform coverage is exactly the platforms in references/INDEX.md.

Contributing to this skill

Change this router only to correct shared concepts or add a pointer to a newly supported platform. Platform-specific operations, errors, and bindings belong under that platform's references/ directory.

Tools

A local command-line client for the platform, run in the configuration directory. Each procedure lists the operations it uses.

Verification checklist

  • Platform confirmed against references/INDEX.md
  • That platform's procedure.md followed, including confirmation gates
  • Apply or destroy used the exact plan the operator reviewed
  • Result reported in the platform's own vocabulary, with partial failure stated

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.