liveBook · Manning

Execution harness

As explained in Spec-Driven Development

An agent harness specialized for independently carrying out tasks and generating implementations or other work products.

An execution harness combines the model’s capabilities with everything around it that helps produce useful work, including tools, skills, prompts, and scaffolding. Specialized harnesses direct that capability toward different tasks, such as knowledge work or software development. section 1.4 section 2.2

The harness acts on context shaped by an intent harness. Specifications can provide a clear target for implementation and validation, reducing reliance on session memory and repeated course corrections. section 2.2 section 2.4

URL shortener

A free-form coding pass asked an agent for changes, inspected the output, and corrected it in a loop, leaving much of the intent in conversation. A specification-driven pass made the specification a durable target for implementation and validation. section 2.4

Figure 1.4 The intent harness is a level above the execution harness and helps us articulate intent to engineer context for the execution harness.

Shows how an intent harness sits above an execution harness, shaping the context that guides its work. section 1.4

How Spec-Driven Development covers it

How deep it goes
Defines the harness and its place in the intent-to-implementation workflow without detailing orchestration internals.
Examples
Contrasts knowledge-work and coding agents, then follows a URL shortener through free-form and specification-guided workflows.
What you can do after
Apply it to implement and validate changes against specifications that provide a clear execution target.
How it connects
Connects agent harnesses with models, tools, intent harnesses, 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.