liveBook · Manning

Specification

As explained in Context Engineering

A description of the requirements, intended behavior, interfaces, and constraints that a software system is expected to satisfy.

A specification, or spec, describes what a software system or change must satisfy. In AI-assisted development, it can serve as a context artifact for a coding agent: it captures intent, constraints, interfaces, edge cases, validation criteria, and nonfunctional expectations before implementation begins. This reduces ambiguity and gives the agent a more stable basis for planning, coding, testing, review, and later changes than a sequence of disposable prompts. section 11.3.7

Specification-driven development distinguishes the desired outcome from the work used to produce it. The specification records what a feature must do and why; a technical plan records the chosen approach; a task list turns that plan into executable work. Keeping these artifacts separate makes the workflow easier to inspect and revise than a long conversation. section 11.5.1

Three approaches differ in how long the specification remains authoritative:

  • Spec-first: write the specification before implementation and use it as the agent’s primary task context. After generation, engineers typically discard it and maintain the code directly. section 11.3.7
  • Spec-anchored: keep the specification aligned with future changes rather than treating it as a one-task artifact. section 11.3.7
  • Spec-as-source: treat the specification as the primary artifact from which implementation is generated. section 11.3.7

Backlog scoring with Spec Kit

For a backlog-scoring feature, the specification captures the feature’s purpose and requirements. GitHub Spec Kit then supports a staged workflow: resolve ambiguity, create a technical plan, break it into tasks, check consistency, and implement after the checks. The resulting artifacts preserve product intent, technical decisions, and coding steps separately for review and reuse. section 11.5.1

Listing 11.2 Compact Spec Kit workflow for the backlog-scoring example
specify init . #1
/speckit.constitution #2
/speckit.specify #3
/speckit.clarify #4
/speckit.plan #5
/speckit.tasks #6
/speckit.analyze #7
/speckit.implement #8

The command sequence shows how the staged workflow moves from specification and clarification through planning, consistency analysis, and implementation. section 11.5.1

A specification is one part of a managed context layer, not a substitute for it. Reliable coding-agent workflows also require current knowledge, controlled tools, evaluation, observability, governance, and operational maintenance. section 11.6

How Context Engineering covers it

How deep it goes
Defines three specification-driven development levels and walks through a staged workflow from intent capture to implementation.
Examples
Illustrates an API endpoint specification and a backlog-scoring feature with separate specification, plan, and task artifacts.
What you can do after
Apply it via GitHub Spec Kit to clarify requirements, plan work, check consistency, and implement a feature.
How it connects
Connects specifications to context engineering, coding agents, technical planning, testing, and software development lifecycle management.

Also explained in

Compare how 12 books explain specification →

Related concepts

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