A field-tested format for writing operational specs that turn AI agents from vague chatbots into reliable crew members. Includes a blank template, two real worked examples, and a completeness checklist.
Most people brief AI agents the way they'd brief a distracted intern: "you're a helpful assistant that does marketing." Then they wonder why the output is generic filler.
An agent without a proper operational spec will:
- Guess at what you want instead of building to a standard
- Produce inconsistent output across runs
- Burn tokens iterating on its own confusion
- Generate work you'd never show a client
An agent with a proper spec does the job once, flags what it can't resolve, and delivers something you'd put your name on.
agent-spec-kit/
├── README.md (this file)
├── TEMPLATE.md (blank spec — fill in your agent)
├── CHECKLIST.md (completeness check before deployment)
├── examples/
│ ├── product-builder.md (worked example: digital product agent)
│ └── content-writer.md (worked example: writing services agent)
└── FORMAT-GUIDE.md (section-by-section breakdown)
- Read
FORMAT-GUIDE.mdto understand what each section does and why it's there - Copy
TEMPLATE.mdand fill it in for your agent - Run through
CHECKLIST.mdbefore deploying - Reference the examples if you get stuck
This format works anywhere you deploy agents:
- IronClaw / OpenClaw
- CrewAI
- LangChain / LangGraph
- AutoGen
- Raw API calls (OpenAI, Anthropic, open-weight models)
- Custom orchestration frameworks
The spec is the briefing document. How you load it into your agent framework is implementation — the principles are the same everywhere.
- Independent operators running AI agent workflows
- Small teams deploying agents for commercial work
- Developers who can build agents but struggle to brief them effectively
- Anyone tired of agents that produce confident garbage
We build automation tools for independent operators. Everything we sell, we use ourselves. Our agents run on specs written in this exact format. When we improve the format, buyers get the update.
Questions: loopwrightdev@proton.me