liveBook · Manning

Context debt

As explained in Spec-Driven Development

Context debt is the absence of durable context needed to safely understand, maintain, and evolve software produced through agent interaction.

Context debt is the absence of durable context needed to safely understand, maintain, and evolve software produced through agent interaction. It accumulates when initial delivery speed takes priority over articulating intent, leaving decisions dependent on agent assumptions and session context. section 2.3.2 section 2.6

Context debt can make agent-assisted changes harder to guide and maintain:

  • When guiding the agent takes as much effort as making the change manually, its leverage is gone. Manual edits still require reconstructing the intent, design, and behavior of generated code. section 2.3.2
  • Context decay is an agent forgetting earlier decisions as its context window fills; cognitive debt comes from accepting code without building a mental model. Context debt leaves us exposed to both. section 2.3.2

A structured, durable specification can preserve intent, constraints, and verifiable outcomes. It need not specify the entire application upfront: when implementation reveals a gap, update the specification and regenerate the implementation. section 2.6

How Spec-Driven Development covers it

How deep it goes
Defines the missing context, explains its consequences, and distinguishes it from context decay and cognitive debt.
What you can do after
Understand how durable specifications preserve intent and support safer evolution of agent-produced software.
How it connects
Links context debt to technical debt, context decay, cognitive debt, and specification-driven development.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Spec-Driven Development. The section links point to the parts of the book it draws on.