Infrastructure automation teams can now build production-ready workflows directly from Claude Code – governed, documented, and deployed in minutes.
Infrastructure automation teams have the platforms. They have the engineers. What they’ve never had is a fast, repeatable way to go from “here’s what we need to automate” to a production-ready workflow – without losing weeks to manual task construction, adapter configuration, and design decisions that live only in someone’s head.
Today that changes.
Itential Skills are now available in the Anthropic Marketplace – installable directly into Claude Code with a single command. Install them, point them at your Itential Platform environment, write a spec describing what you need to automate, and let the agents build it. Governed, tested, documented – not a prototype that needs cleanup.
Itential Agentic Builder Skills are a set of AI agent skills for Claude Code that implement Spec-Driven Development (SDD) for infrastructure automation. They give Claude Code the domain knowledge it needs to build real things inside the Itential Platform – not generic code, not scaffolding, but production-ready workflows, form entries, command templates, lifecycle manager assets, IAG services, and more.
The package includes 1 plugin, 13 skills, and 3 delivery agents – purpose-built for infrastructure automation delivery on the Itential Platform. The three delivery agents map directly to the five stages of the SDD lifecycle:
Three agents because the goal isn’t agent proliferation. The goal is lifecycle clarity. Each agent has a defined responsibility, and each stage produces a named artifact that gates the next.
Note: Itential Skills run in Claude Code – Anthropic’s CLI-based agentic coding tool – not the claude.ai chat interface. If you’re new to Claude Code, start here.
Once installed, the skills can generate and deploy the following directly into your Itential Platform environment:
Everything built is deployed, tested, and documented – not handed back to your team as something that still needs finishing.
The skills implement a five-stage delivery lifecycle – the same model covered in depth here:
Each stage produces a named artifact. Each artifact requires human approval before the next stage begins. AI agents execute the work – engineers control the gates.
In practice: you write a spec file. It’s a plain-language markdown document that describes what the automation needs to do – the entry point, the workflow logic, the form fields, the systems involved. The skills read it, bootstrap your environment, discover your available adapters, and build.
You define the intent. The agents handle the construction. And every decision along the way is documented – so the next person to touch it isn’t starting from scratch.
Delivery Skills – the SDD lifecycle:
| Skill | What It Does |
|---|---|
spec-agent |
Locks requirements – refines the use case into an approved spec |
solution-arch-agent |
Feasibility + Design – assesses your platform, produces the solution design |
builder-agent |
Build + As-Built – implements the approved design, tests, delivers, and documents |
flowagent-to-spec |
Takes an existing FlowAgent and produces a deterministic workflow spec |
project-to-spec |
Reads an existing project and produces spec + design documentation |
explore |
Authenticates to your platform and lets you browse what’s available |
Platform Skills – direct platform operations:
| Skill | What It Does |
|---|---|
flowagent |
Create and run AI agents with LLM providers, tools, and missions |
iag |
Python, Ansible, and OpenTofu via iagctl |
itential-mop |
Command templates with validation rules |
itential-devices |
Device management, backups, diffs, groups |
itential-golden-config |
Golden config, compliance grading, and remediation |
itential-inventory |
Device inventories, nodes, actions, and tags |
itential-lcm |
Resource models, instances, and lifecycle actions |
The repository ships with 22 technology-agnostic spec files covering the most common infrastructure automation use cases – ready to use as starting points with spec-agent.
Each spec is a starting point – customizable to your environment, your adapters, your constraints.
The point isn’t to hand you a finished product. It’s to remove the blank-page problem and give teams something real to react to.
1. Start fresh with new work
Run the full SDD lifecycle from scratch. Write a spec (or start from one of the 22 examples in the repo), run spec-agent, and deliver through all five stages.
2. Productionize exploratory agent work
If you’ve been using FlowAgent to explore automation ideas, use flowagent-to-spec to move that output into a real, governed delivery path with proper documentation.
3. Bring existing automation under governance
Use project-to-spec to read an existing Itential project – documented or not – and produce a retroactive spec and solution design. The automation your team built three years ago that nobody can fully explain anymore? That’s a real problem, and this is where you start fixing it.
Early access (available now):
/plugin marketplace add itential/builder-skills
/plugin install itential-builder@itential-builder
Then copy an environment template and configure your platform credentials:
cp environments/cloud-lab.env my-use-case/.env
Full setup and first delivery walkthrough: docs/quickstart.md
Official Anthropic Marketplace install (once approved):
/plugin install itential-builder@claude-plugins-official
The repo is public: github.com/itential/builder-skills
This is v1. The spec library will grow. The skills will deepen. And I expect the community will build use cases we haven’t thought of yet – that’s the part I’m most interested to see.
If you hit something that doesn’t work, open an issue. If you have a use case you want to see in the spec library, start a discussion. The repo is public and contributions are welcome.
Most infrastructure teams I’ve talked to over the years aren’t short on ambition – they’re short on time and bandwidth to build automation the right way. A delivery model that removes the construction burden without removing the engineer from the decisions is a meaningful shift. This is that.
Try it: github.com/itential/builder-skills
Want to see the full lifecycle from spec to deployed workflow? Watch Joksan Flores, Principal Solutions Engineer, build a DNS A record provisioning workflow end-to-end – form-triggered, Infoblox-integrated, and live in Operations Manager in under two minutes.
See how Itential connects AI reasoning to governed execution across your entire infrastructure.