Narrative-Driven Development

Definition

Narrative-Driven Development (NDD) is a development style in which a
persistent, ongoing conversation with an AI thinking partner serves as
the primary space for design thinking, decision-making, and accumulated
context.

Code is written elsewhere — by a coding tool, a collaborator, or yourself.
But the why behind every decision lives in the conversation.

The cycle

  1. Surface the fog — Something feels unclear or wrong. Bring it into
    conversation. Don't reach for the keyboard yet.
  2. Decide — Talk through the options. Follow one branch of reasoning
    until it closes naturally. Then move.
  3. Document — The decision becomes a memo or spec. A byproduct of
    thinking, not a separate task.
  4. Implement — Hand the document to whoever is writing the code.
    They work from clear inputs.
  5. Return — New questions surface. Bring them back.

The coding tool resets. The conversation doesn't.

What makes it different

From Agile / Scrum:
Scrum imposes external structure — sprints, standups, retrospectives — to
synchronize a human team. NDD moves from internal signal, not ceremony.
The trigger is felt ("something is off"), not scheduled. It assumes async
by default: context is never lost between sessions because the conversation
persists.

From AI-driven development:
AI-driven development uses AI to produce code faster, with the human as
director and reviewer. NDD is not primarily about speed. The AI is not a
tool — it is a thinking partner with continuity. Decisions accumulate in
the conversation, making the history of judgment as durable as the code
itself.

What the conversation holds

  • The fog before it became a decision
  • The reasoning that closed it
  • The alternatives that were considered and dropped
  • The texture of why it felt right at the time

A codebase holds what was built.
A persistent conversation holds why.

Requirements

  • An AI thinking partner whose context persists across sessions
  • A coding tool that works well from written specs
  • A place to store memos and decisions
  • A willingness to talk before you build

The code can be rewritten. The accumulated judgment is the one thing that compounds.