The Journey
From fourteen articles to a framework
Intent-Driven Development did not arrive fully formed. It was worked out in public, one article at a time, between January and March 2026, right here on this site.
The starting question was simple. As AI, and more specifically agentic AI, takes on more of the execution of software, what is left for humans to do, and how should teams organise around it? The answer that emerged is that the primary human contribution shifts from writing code to governing intent: specifying what should be built, why, and within what boundaries, then holding AI execution accountable to that intent.
Over fourteen articles, that idea grew a vocabulary and a structure: Intent Specifications, Intent Fidelity, Risk Dials, the Intent Hierarchy, Human Gates, the Autonomy Boundary, and a maturity model for adopting it all. Each article tested one part of the argument. Together, they became the foundation of the framework.
Those original fourteen pieces remain published below, exactly as the thinking developed. The complete framework, refined, restructured, and expanded, now lives at intentdrivendevelopment.org, where you can also download the free ebook.
01
Intent-Driven Development (IDD)
The article that started it all. Naming the methodology and the core shift from writing code to governing intent.
02
How IDD Bridges UCD, DDD, BDD, and TDD in the AI Era
Placing IDD in the lineage of the disciplines that came before it, and showing what it inherits from each.
03
Human Gates in Agentic Flows for Enterprise AI Control
Where humans must remain in the loop, and how to design deliberate checkpoints into agentic workflows.
04
Why IDD Survives Rapid AI Model Evolution
Why a framework anchored in human intent stays relevant no matter how quickly the underlying models change.
05
Intent-Driven Development via Multi-Agent Systems
Applying IDD when execution is delegated not to one agent but to orchestrated systems of them.
06
The measurement question: how closely does what was built match what was intended, and how do you know?
07
A staged path for teams and organisations adopting IDD, from first experiments to embedded practice.
08
Designing Intent at Scale – How Enterprise Roles Evolve in the Age of AI
Lifting the lens from the team to the enterprise, and what happens to roles when intent becomes the unit of work.
09
The skills, judgement, and posture of the engineer whose job is now governing intent rather than typing code.
10
How Do You Specify Your Intent?
The practical heart of the framework: what an Intent Specification actually needs to contain.
11
How intent cascades through Organisation, Domain, and Project levels, and how the layers stay coherent.
12
Intent Evolution and Intent Shaping
Intent is not static. How specifications evolve, and the discipline of shaping intent as understanding grows.
13
Turning every cycle of intent, execution, and review into organisational learning that compounds.
14
Humans Have Roles, Agents Have Functions
The closing distinction of the series: accountability lives with people, capability can live anywhere.
The Outcome
The complete framework, in one place
In April 2026 the fourteen articles were refined, restructured, and expanded into a complete framework with its own home. It includes the full methodology, the glossary of IDD terms, and the free ebook, Intent-Driven Development: Where Human Intent Meets Machine Execution.
If you only visit one link on this page, make it this one.
Beyond Software
What came next: Human Intent
IDD answers the question for software engineering. But the same principle, govern intent, delegate execution, does not stop at the codebase. The Human Intent series takes the argument to the whole organisation: what happens to structures, roles, and leadership when work is no longer the unit being organised.
Start the Human Intent series →
Human Intent – Organisational Change in the AI Era: the shift from managing work to governing intent.














