liveBook · Manning

Task phase

As explained in Spec-Driven Development

The specification phase in which engineering decomposes design work into executable tasks and defines completion evidence.

The task phase translates a design into a detailed task list for an agent to execute. Engineering decomposes the work and defines evidence that can support the agent’s claim of completion. section 2.2.1 section 4.1.1

The task list draws on Discover’s definition of what to build and Design’s technical approach. Engineers author it with the agent and refine the specification through feedback; for example, QA can flag acceptance criteria that are too imprecise to test. section 2.2.1 section 4.1.1

Figure 2.5 Overview of the Task phase in SDD.

Overview of the Task phase in the specification workflow. section 2.2.1

How Spec-Driven Development covers it

How deep it goes
Describes task decomposition and completion evidence, without detailing a step-by-step task-authoring procedure.
Examples
Uses a QA engineer’s feedback on acceptance criteria that are too imprecise to test.
What it assumes
Builds on Discover’s definition of what to build and Design’s technical approach.
What you can do after
Apply the design by defining executable tasks and evidence for completion.
How it connects
Connects Discover and Design to acceptance criteria, testing, and agent execution.

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.