{+} MISSION+ACDC · Agent Centric Development Cycle
01 / The loop
The spec is the
new source code.
The MISSION+ delivery cycle for agentic engineering. Humans set the intent, agents build, automated tests decide what passes, and working software ships. Each loop faster than the last.
ACDC
AgentCentricDevelopmentCycle
01
Specify
Humans
Intent, constraints, acceptance criteria.
→02
Build
Agents
Plan, write, test and fix on a loop.
→03
Validate
Tests + humans
Quality gates before the next cycle.
→04
Ship
Production
Fast, documented, audit-ready.
↻ Each loop gets tighter as the spec library matures
02 / The shift
The questions change.
When agents write the code, the human's job moves up the stack — from typing fast to thinking clearly.
The old reflex
How do I write this?
Can I code it fast enough?
shifts to→
The new focus
Can I specify it clearly?
How do I validate this?
03 / The proof
3 people now build what took 10.
4–6
Features per sprint, per dev
3–10×
More code shipped per day
~50%
Less time debugging
$20K
Monthly tooling, all-in
"
Agentic coding is when you are not writing the code directly 99% of the time.Andrej Karpathy · Feb 2026
04 / Where it sits
One stage of the MISSION+ pipeline.
AURAReadiness assessment
→
ATOMOperating model · the wrapper
→
You are hereACDCDelivery lifecycleThe delivery lifecycle that turns specs into shipped software. One continuous build-and-validate loop.
▲ Feeds validated ideas
REXInnovation pipeline
+ Supporting capabilities
AI LiteracyPathfinderGovernanceLegacy Modernisation
Put the loop to work.
See the ACDC cycle running on your codebase — from spec to shipped, in one engagement.
AURA→ATOM→ACDC→Spec Ops · Greenfield