liveBook · Manning

Structured conversation

As explained in Spec-Driven Development

An interaction structured to elicit missing information and capture software intent in a specification.

Structured conversation elicits intent that would otherwise remain implicit, captures it in durable artifacts, and gives an agent context to act on. It turns an initial idea into usable, progressively more precise requirements. section 1.4 section 1.2

The format matters less than the conversation it enables. User stories establish whose need is being addressed and why; acceptance criteria make concrete, verifiable behavior explicit. These shared artifacts align business and technology rather than passing requirements between them. section 1.2

Password reset

A story identifies the account holder’s need to regain control of an account. Follow-up scenarios specify that a successful reset invalidates existing sessions and that a link expires after 30 minutes. The discussion makes security behavior part of the recorded intent. section 1.2

Listing 1.2 Acceptance criteria password reset user story
Scenario: Resetting a password revokes existing access
 
Given I am an account holder with one or more active sessions
And I have requested a password reset
When I successfully set a new password using the reset link
Then all existing sessions for my account are invalidated
And I must log in again on any device
 
Scenario: A reset link is valid only for a limited time
 
Given I have requested a password reset
When I open the reset link within 30 minutes
Then I am allowed to choose a new password
 
Scenario: An expired reset link cannot be used
 
Given I have requested a password reset
When I open the reset link after 30 minutes
Then the link is rejected
And I am prompted to request a new one

Review the password-reset scenarios as an example of turning intent into verifiable behavior. section 1.2

When implementation exposes an intent gap, improve the workflow where that intent was lost:

  • If a question was never asked, improve the authoring dialogue; if a decision was captured too loosely, strengthen the specification. section 3.2.5

How Spec-Driven Development covers it

How deep it goes
Develops dialogue through user stories and acceptance criteria, then connects missed intent to workflow improvements.
Examples
Uses password-reset stories and scenarios for session invalidation and expired links.
What you can do after
Apply stories and acceptance criteria to clarify feature intent and record verifiable behavior for implementation.
How it connects
Connects user stories and acceptance criteria with Behavior-Driven Development and Test-Driven Development.

Also explained in

Compare how 4 books explain structured conversation →

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.