liveBook · Manning

Intent elicitation

As explained in Spec-Driven Development

Intent elicitation is the process of drawing out a person's intended purpose, requirements, and constraints through interaction.

Intent elicitation draws out and aligns purpose through dialogue among people and AI. Shared context and recorded decisions help a specification guide implementation beyond the initial interaction. section 2.5.2 section 2.1

Build intent collaboratively and preserve it in a specification:

  • Bring product, architecture, engineering, and quality perspectives together; each contributes distinct knowledge about user needs, system fit, constraints, and implementation. section 2.5.2
  • Use AI to surface assumptions and ask clarifying questions, supporting dialogue rather than simply handing over instructions. section 2.5.2
  • Capture decisions, implementation constraints, and outcome verification in a durable specification that can guide execution and future changes. section 2.1

Prompt file or specification?

Saving a prompt or an agent's plan to a file does not by itself make it a specification. A specification also articulates intent, sets constraints, defines verification, and preserves reusable guidance. section 2.1

How Spec-Driven Development covers it

How deep it goes
Explains dialogue, assumption-surfacing, and specification criteria without prescribing a detailed elicitation script.
Examples
Contrasts a prompt or plan saved to a file with a specification that records intent, constraints, and verification.
What you can do after
Evaluate whether a captured artifact preserves intent by checking for constraints, outcome verification, and durability.
How it connects
Connects intent elicitation to specifications, context engineering, and specification-driven development.

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.