Specification authoring
Specification authoring is the process of eliciting and expressing a system’s required behavior, constraints, and acceptance conditions.
Vibe Engineering
The process of defining a system's required behavior, constraints, and acceptance conditions.
- How it is used
- Makes product intent explicit and enforceable before final implementation, while using prototypes to discover rules and edge cases.
- How deep it goes
- Works through prototype discovery, executable scenarios, artifact generation, and review, while emphasizing that specifications and tests remain incomplete.
- Examples
- Uses refund approval and rejection scenarios, time-boundary probes, and an ISBN validation case involving spaces.
- What you can do after
- Practice authoring reviewable behavior scenarios and using AI to propose testable artifacts and overlooked cases.
Read how Vibe Engineering explains specification authoring →
Spec-Driven Development
Specification authoring is the structured process of eliciting intent and expressing it as a detailed feature specification.
- How it is used
- Turns feature ideas into specifications that guide a coding agent's implementation and verification.
- How deep it goes
- Outlines Discover, Design, and Task as separate conversations and explains their artifacts; does not provide a detailed authoring checklist.
- Examples
- Uses a three-phase workflow and an engineer-as-scribe scenario to show how artifacts progress and intent can be lost.
- What you can do after
- Practice/perform incremental specification authoring before agent execution, then reuse and revise specifications as project context.
Read how Spec-Driven Development explains specification authoring →
Related concepts
- designhas part · Design is the process of planning and specifying an artifact’s structure, behavior, or presentation, and the resulting arrangement, to meet intended purposes and constraints.
- discoveryhas part · Discovery is the process of identifying, locating, or examining information, entities, problems, or opportunities relevant to a particular purpose.
- task phasehas part · The Task phase is the specification phase that decomposes an approved technical approach into executable implementation tasks.
- pull requestused by · A pull request is a version-control proposal to integrate changes from one branch or repository into another, typically supporting review and discussion before merging.
- specificationproduces · A specification is a description of the requirements, expected behavior, properties, interfaces, or constraints that a system or component is expected to satisfy.
Questions about specification authoring
What is specification authoring?
Specification authoring is the process of eliciting and expressing a system’s required behavior, constraints, and acceptance conditions.
Which Manning books explain specification authoring?
Vibe Engineering and Spec-Driven Development.
What are the parts of specification authoring?
Specification authoring includes design, discovery and task phase.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

