01Engineer
Intent
Frames the problem as a spec: the goal, the constraints, and what "done" means. This is where engineering judgment has the most leverage.
Watch the deep dive →
Interactive
The Agentic Development Life Cycle, in motion.
Follow work from an engineer's intent through planning, coding agents, deterministic verification gates, human review, release, and observation — and back again. Agents carry the volume. Engineers make the calls that matter.
- Engineer
- Agent
- Deterministic gate
- Auto-fix loop
Who does what
Hover a stage to find it on the loop.
02Planner agent
Plan
Breaks the spec into tasks after reading the steering files — architecture rules, conventions, guardrails. The engineer can veto the plan before any code is written.
Watch the deep dive →03Coder agents
Build
Several agents implement tasks in parallel, each in its own sandbox. They are fast, cheap, and confident — which is exactly why the next stage exists.
Watch the deep dive →04Gates + critic agent
Verify
Tests, type checks, schema contracts, AST security scanning, and a critic-agent review. Failures loop straight back to Build with the error attached, so no human reviews code that hasn't passed.
Watch the deep dive →05Engineer
Review
Human attention goes to what machines can't verify: is this the right change, what are the trade-offs, what's the blast radius. The engineer approves or redirects.
Watch the deep dive →06Deploy agent
Release
Ships behind feature flags with a canary rollout, and rolls back automatically on an SLO breach.
Watch the deep dive →07Monitor agent
Observe
Watches telemetry and user signals, and turns anomalies and opportunities into new intents for an engineer to frame — closing the loop.
Watch the deep dive →Go deeper: What is the ADLC? · The new engineering archetype · Building verification layers