From SDLC to AI-DLC

Yesterday vs. Today

Day 1 — we gave the agent hands (MCP) and saw the loop run.

Day 2 — we decide who's driving the whole build,
and what process keeps it honest.

The question today: when an AI can write the code,
what does the development lifecycle become?

The Classic SDLC

The way software has been built for decades:

Requirements → Design → Build → Test → Deploy → Maintain

• Human-driven at every stage
• Iterations measured in weeks (Agile sprints)
• Documentation is a by-product, written after — if at all
• Process designed around slow, human throughput

It works. But it was built for a world where humans write every line.

What Breaks When AI Enters

Drop a fast code-generating AI into the classic SDLC and the seams show:

• The bottleneck moves from writing code to deciding what to build
• "Sprints in weeks" is absurd when a feature can be generated in minutes
• The AI fills undefined gaps with guesses — silently
• Context is lost between sessions; the AI forgets yesterday

The process is now the slow part — not the coding.

The "Whitespace" Problem

Traditional Agile leaves areas undefined — the whitespace between stories, specs, and decisions. Humans quietly fill it with judgment.

An AI fills that same whitespace too — but with assumptions you never see.

The result:

• Inconsistent architecture decisions
• Missing design documentation
• Quality issues from skipped steps
• Context loss between iterations

Whitespace was survivable when humans filled it.
With AI, unspecified means hallucinated.

Enter AI-DLC

The AI-Driven Development Lifecycle.

A reimagined methodology where
AI drives the conversation — and humans validate.

• Developed by AWS; productized by tools like specs.md
• Replaces week-long Sprints with hour/day-long Bolts
• Turns documentation from an afterthought into the engine

Same goal as BMAD: make the spec the thing that drives the build.
AI-DLC is the industry name for the shift we're practicing.

The Core Inversion

The single biggest mental shift:

Traditional: humans drive, AI assists.
AI-DLC: AI drives, humans validate.

You stop writing the work and start steering and approving it.

This is the "architect, not coder" promotion —
stated as a lifecycle, not just a job title.

The Four Principles

AI-Driven — AI leads the conversation, proposes solutions, generates artifacts. Humans guide.

Rapid Iterations — Bolts replace Sprints. Meaningful work in hours, not weeks.

Human Checkpoints — validation at each gate catches errors before they cascade.

Design-First — design technique (DDD) is built into the build, not bolted on after.

Speed from AI · safety from checkpoints · quality from design-first.

Sprints → Bolts

The unit of work itself changes:

When generation is near-instant, the iteration shrinks to match.

The Three Phases

AI-DLC organises work into three phases, each with a specialised agent:

Inception → Construction → Operations

• A Master Agent coordinates
• Each phase has a clear purpose and concrete outputs
• Human checkpoints sit between and within phases

Notice the shape: this is orchestrator + sub-agents —
the multi-agent pattern from Day 1, applied to a whole lifecycle.

Phase 1 — Inception

Key outputs — user stories, non-functional requirements (NFRs), unit definitions.

This is the spec. Nothing gets built until intent is explicit.
(In BMAD terms: PRD + Tech Spec live here.)

Phase 2 — Construction

Key outputs — domain models, code, tests.

This is where the agent builds — but inside guardrails.
(In BMAD terms: Story Map + Task List drive this; the Developer persona executes.)

Phase 3 — Operations

Key outputs — deployment units, runbooks.

The lifecycle closes where Day 1's finale pointed:
a real thing, live and observable.

How AI-DLC Fixes the Whitespace

The problems, and the answers:

Every fix is something we've already named:
specs, checkpoints, durable memory.

Checkpoints — Right-Sizing the Process

Not every change deserves the same ceremony. A useful model:

• Trivial task → few or no checkpoints
• Standard feature → one validation gate
• Critical/irreversible change → multiple gates

This is the simplicity principle from Day 1, applied to process:
add oversight where risk is — not everywhere.

When AI-DLC Is the Right Choice

Reach for the full methodology when:

• A team needs coordination
• The domain is complex and benefits from DDD
• You need documentation and traceability
• You're in a regulated / audited environment

For a quick script, this is overkill — use less process.
Match the method to the stakes.

AI-DLC and BMAD — Same Shift, Two Lenses

Don't let the vocabulary confuse you. They rhyme:

AI-DLC is the lifecycle framing (the why and shape).
BMAD is how we actually do it this weekend.