The ABCDE Of Agent-Driven Development
On this page
- From an idea to a merged PR
- Is this for you?
- The lifecycle, stage by stage
- The walkthrough
- A — Add: park the idea
- B — Brainstorm: sharpen the decisions
- C — Code: build it in isolation
- D — Deliver: ship the PR
- E — Explore: what's next
- Behind the simplicity: the pillars
- Add — capture the spec
- Brainstorm — resolve decisions
- Code — build in isolation
- Deliver — ship it
- Explore — what's next
- The branching model
- Try it yourself
Related Articles
Give Claude Code A Visual Language
Turning a client-rendered app into a server-rendered one is not a pull request. It is six of them, in an order that matters, over three weeks — and by the second week nobody can answer "where are we?" without twenty minutes of scroll-back. Here is the shape that fixed it — one outline artifact, one step per pull request, and a link that points both ways.
Give Claude Code A Voice
An agent that works for ten minutes has exactly two moments worth interrupting you for — it finished, or it is stuck waiting on you. Two hook events, two one-second voice notes, and about six lines of settings.json. Includes both sounds, playable here, and the details that will bite you if you wire this up carelessly.
What Is An Agent Harness? The Pattern Behind Every AI Coder
A deep dive into agent harnesses — the loop that wraps an LLM and turns it into something that can read files, run tests, and ship code. We break down the six parts, the turn loop, the design tensions, and build one in 30 lines of TypeScript.
Google Gemma 4 And TurboQuant Explained For Web Developers
A deep dive into Google's Gemma 4 open model family and TurboQuant KV cache compression — what they are, how they work, and why they matter for developers building AI-powered applications.