Intent-Driven Development Framework
A process framework that gives developers and AI agents enough context to make decisions autonomously — without waiting for someone to tell them what to do.
The Problem
In most agile teams, knowledge lives in the Product Owner's head. Developers wait for clarification. AI agents guess when context is missing. Every ambiguous user story becomes a decision bottleneck — someone has to ask a question, wait for an answer, or make an assumption and hope it's right.
Traditional agile methodologies were also designed for a world where human coding capacity was the primary constraint. AI coding agents have changed that equation. When the build phase compresses 5–10x, the bottleneck shifts from building to defining, reviewing, and validating — and every gap in context produces wrong output at machine speed.
The frameworks haven't caught up. Teams are using 2-week sprints to manage work that takes 2 hours to build. They're estimating story points for tasks where effort is no longer the dominant variable. They're holding planning meetings to decompose work that AI agents can execute from a well-written specification.
The Framework
Intent-Driven Development (IDD) replaces work-decomposition with purpose-decomposition. Instead of asking "what should developers work on this sprint?" IDD asks "what does this product need to be, and how do we know it's right?"
The core principle: The IDD hierarchy is not a chain of command — it's a chain of context. Each layer gives developers and AI agents the information they need to make implementation decisions independently, without waiting for someone above them to answer questions. When a developer understands why the product exists (Product), what it should accomplish (Intention), how we'll know it's right (Expectation), and what's in and out of scope (Spec with Boundaries), they can execute autonomously and make better decisions than any planning meeting could prescribe.
The Hierarchy
Product → Why does this exist?
└─ Intention → What should it accomplish?
└─ Expectation → How do we know it's right?
└─ Spec → How does AI build it?
| Level | Replaces | Purpose |
|---|
| Product | Epic / Program | Define the problem space, vision, and value proposition |
| Intention | Feature | Describe what the product should accomplish |
| Expectation | Acceptance Criteria | Specify verifiable constraints with edge cases |
| Spec | User Story + Tasks | Provide AI-ready build instructions |
Key Differences from Traditional Agile
- Autonomy through context — developers and AI agents get enough information to make decisions without waiting for clarification
- Continuous flow with WIP limits replaces time-boxed sprints
- Spec quality is the primary throughput metric, not velocity
- Completeness gates prevent underspecified work from reaching AI agents
- Boundaries (what AI must not do) are a first-class artifact field
- Context inheritance eliminates repeated boilerplate across specs
- A new Spec Author role bridges business intent and AI execution
Quick Start
- Understand the philosophy →
docs/autonomy.md — why context enables autonomy
- Read the framework →
docs/framework.md — the complete process definition
- See it in action →
examples/ — a worked example using the full hierarchy
- Use the templates →
templates/ — copy-paste starter templates for each artifact
- Understand the roles →
docs/roles.md
- Set up metrics →
docs/metrics.md
Documentation
| Document | Description |
|---|
| Autonomy Through Context | The core philosophy — how the hierarchy enables developer autonomy |
| Framework | Complete process definition — artifacts, lifecycle, ceremonies |
| Artifacts | Detailed definitions and field reference for Product, Intention, Expectation, and Spec |
| Spec Authoring Guide | How to write AI-ready Specs — with do's, don'ts, and the completeness checklist |
| Roles | Role definitions and responsibilities in IDD |
| Metrics | Primary and secondary metrics for measuring process health |
| Adoption Guide | How to pilot IDD with your team |
| FAQ | Common questions and concerns |
