A specification agent turns requirements into instructions a coding agent can follow. This part covers the agent-spec.md structure, how developers validate it, AGENTS.md and guardrails, the development loop and the handover file.
The first two steps of the agentic pipeline have no agent in them. Here is how the product owner writes value.md, how developers turn it into requirements.md, and why a human gate before the specification agent is the brake the process needs.
AI coding agents eat user stories faster than a product owner can write them. Here is a spec-driven, agentic pipeline that spreads the work across people and agents, keeps humans at every gate, and keeps everything in the repository as markdown.
Intro I talk a lot about AI these days… and I know I am not alone. People talk a lot about “agentic AI” or “AI Agents” or simply “Agents”. During these discussions, I see there is confusion sometimes what is an Agent and what’s the difference between “AI” and “AI Agents”. Here’s the core distinction, […]
