Spec-Driven Development for Agentic Operations with Itential

What’s In This Guide

Three Agents, Five Stages

The Spec Agent, Solution Architecture Agent, and Builder Agent – what each is authorized to do, what artifact it produces, what it cannot do, and how artifact-based handoffs govern the transition between stages.

Five Agents, Any LLM

The Itential Skills package ships with five agents that work with any LLM. Three are the SDD delivery agents that execute the five stages – Spec Agent, Solution Architecture Agent, Builder Agent. Two are Itential Platform agents for agentic operations and governed conversion of existing agent work. All five invoke governed API skills against your actual infrastructure.

The Trust Progression

Three stages from AI-assisted to governed autonomy – what each looks like operationally, what earns the right to advance, and where most production teams should operate today.

Who This Guide Is For

The Problem with Unconstrained Agent Execution

An AI agent that operates on network and infrastructure without a governing operating model is not autonomous operations. It is unaccountable automation. The agent makes decisions at machine speed against requirements that were never formally agreed, in an environment it may not have fully validated, producing outputs with no authoritative record of what it changed or why.

This is not a hypothetical risk. It is the predictable outcome of deploying AI agents without the structural foundations that make human-executed automation trustworthy – approved requirements, reviewed designs, enforced phase boundaries, and a reconciled record after delivery. AI acceleration without those foundations does not eliminate the structural failures of informal practice. It reproduces them at machine speed and at larger scale.

The organizations advancing toward agentic operations safely are not doing so by constraining what their agents can do. They are doing so by ensuring agent execution occurs inside a governing operating model – one that defines the boundaries of agent authority, enforces phase transitions, and produces an auditable record of every action. SDD is that operating model. Itential is the platform that makes it executable.

The Execution Model – Three Agents, Five Stages: How Itential Executes SDD

Itential operationalizes the five SDD stages through three named agents. Each agent owns specific stages, is authorized to access specific platform capabilities, produces required artifacts, and cannot advance past a gate without explicit approval. The agent is the execution mechanism. The SDD operating model is the boundary that defines what it is authorized to do.

Govererned API Skills – Five Agents, Every Integration Surface as a Governed API Skill

The agents above execute the SDD lifecycle. What they execute against is the platform’s governed skill library – every system your automation touches, exposed as an API skill the platform orchestrates against the approved spec. Not open API access engineers manage themselves. Skills with defined inputs, defined outputs, and defined access boundaries that execute within the governance envelope the operating model establishes.

The Itential Skills package ships with five agents and works with any LLM. Three of those agents are the SDD delivery agents – they map directly to the five stages and own the lifecycle from requirements through as-built. The other two are Itential Platform agents that extend beyond the SDD lifecycle for agentic operations and governed conversion of exploratory work. The platform skills below are what all five agents invoke against your actual infrastructure.

SDD Delivery Agents – 3 Agents, 5 Stages

Three agents execute the five SDD stages. Each owns specific stages, produces a required artifact, and cannot advance past a gate without explicit approval. These are the agents that operationalize the operating model.

Itential Platform Agents – Agentic Operations on the Platform

Two additional agents extend the skills package beyond the SDD lifecycle. These operate directly on the Itential Platform – one for creating and running AI-powered agents within the platform, one for converting existing agent work into governed SDD deliveries.

Utility Skills – Retrofit & Discovery

Network & Device Skills – Governed Access to Network Infrastructure

Infrastructure & Cloud Skills – Governed Access to Infrastructure APIs

The Audit Record – The Artifact Chain as the Audit Record

Every SDD engagement executed through Itential produces a complete, linked sequence of artifacts – from the initial approved spec through the reconciled as-built record. This is the audit record. Every decision from intent to production state is traceable to the artifact that authorized it.

This chain answers the questions that informal practice cannot. What was the original requirement? What did feasibility find? What did the design approve? What was actually built? Where did it deviate and why? Every question an auditor, a compliance team, a future engineer, or a subsequent agent might ask is answered by the artifact chain – not by inspecting workflow code or relying on whoever built it to remember.

For agentic operations, the artifact chain is what makes machine-speed execution auditable. An agent that deploys automation in twenty minutes leaves the same artifact trail as a human engineer working over two weeks. The speed changes. The accountability does not.

What the Chain Enables on Day 2

Every Day 2 engagement – extension, debug session, modification, handoff – starts from the reconciled as-built record rather than from archaeology. The next engineer knows exactly what was built, what deviated from the design, and why. The next agent can be scoped against the same artifact chain. The compliance team has the evidence package they need without a post-delivery documentation sprint. The automation estate compounds rather than accumulates debt.

The Governed Autonomy Progression

Itential is the agentic operations platform for network and infrastructure automation. Agentic operations in Itential follow a trust progression – not a capability ladder, but a governance model. Each stage increases the scope of agent authority based on demonstrated reliability of agent execution. Human oversight shifts from execution-level to gate-level to policy-level. The SDD operating model remains constant throughout. What changes is who performs each stage and at what level humans maintain decision authority.

The progression from Stage 1 to Stage 3 is earned, not assumed. Stage 3 autonomy for VLAN provisioning on a mature, reconciled automation estate is reasonable. Stage 3 autonomy for a new integration class with no prior as-built record is not. The artifact chain is what makes the advancement decision defensible – each engagement’s as-built record is evidence of agent execution quality that can be assessed before trust is extended further.

The Spec Library – 22 Ready-to-Use Starting Points

The Itential Builder Skills ship with 22 technology-agnostic High-Level Design specs – one for each of the most common network and infrastructure automation use cases. Each spec is a starting point, not a template to follow verbatim. Hand it to the Spec Agent, tell it what’s different about your environment, and it refines it for your specific infrastructure before kicking off a delivery.

The specs are available in the Itential Builder Skills GitHub repo. Clone the repo, pick the spec closest to your use case, and use the Spec Agent to refine it for your environment before kicking off a delivery. The repo also includes example environments and helpers – JSON scaffolds for workflows, templates, and projects – that accelerate the Build stage.

Getting Started – Entry Points by Automation Maturity

The right starting point depends on where your team is today. Three practical paths based on your current automation state.