liveBook · Manning

Product specialist

As explained in Spec-Driven Development

A product-side participant who clarifies feature intent and defines what a feature should accomplish.

A product specialist defines what needs to be built, for whom, and why. In specification work, this is the Discover phase: architects define the technical approach, and engineers break the work into executable tasks and completion evidence. Feedback from implementation and testing can refine the specification, including unclear acceptance criteria. section 4.1.1

Feature work can also establish standing context for future specifications:

  • Record business rules that apply across the product, not just to one feature. section 4.2.1
  • Define shared business vocabulary so specifications can use precise, consistent terms. section 4.2.1
  • Make authors consider who a capability serves, how failures appear to users, and what is out of scope. section 4.2.1

Short-link rules

When specifying anonymous short-link creation, define that each destination must be a valid URL and must not itself be another short link. Because links may be embedded in published material, a link that stops resolving is a serious failure. These rules apply beyond the feature and belong in standing context. section 4.2.1

Figure 4.1 A mental model of participation of key stakeholders in authoring specification as part of Intent Harness.

Use the stakeholder diagram to see how product, architecture, and engineering contribute to specification authoring. section 4.1.1

How Spec-Driven Development covers it

How deep it goes
Develops feature intent into reusable business rules, shared vocabulary, and mandatory specification questions.
Examples
Uses short-link creation to establish valid-destination and no-chaining rules, and to consider failure consequences.
What you can do after
Apply the role by defining feature purpose, audience, business rules, failure behavior, and explicit scope.
How it connects
Coordinates with architects on technical design and engineers on executable tasks, acceptance criteria, and completion evidence.

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.