liveBook · Manning

Chapter 4: Collaborating Across Product, Architecture, and Engineering

What you will learn in chapter 4 of Spec-Driven Development

The chapter introduction explains why teams need shared specifications to onboard memoryless AI agent sessions and turn individual AI gains into team productivity.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The chapter introduction explains why teams need shared specifications to onboard memoryless AI agent sessions and turn individual AI gains into team productivity.

Key terms: agent session, new joiner, tribal knowledge, SDD workflow, Intent Harness, specifications, intent, specification authoring, team productivity, agent onboarding

4.1 Moving beyond solo SDD: collaboration patterns

This section explains why team-based SDD lets specialists contribute their own intent through a shared specification without requiring everyone to become a generalist.

Key terms: specification, common control surface, intent, coding agent, solo SDD, generalist, specializations

4.1.1 Three roles at the specification surface

This section maps three contributing roles to specification phases, distinguishes specification authoring from execution, and shows how engineering feedback refines the spec.

Key terms: product specialist, architect, Engineering, Discover, Design, Tasks, Intent Harness, Execution Harness, specifications, implementations

4.1.2 Engineer as scribe

This section explains why having an engineer write everyone else’s specification input is a common but unsustainable collaboration pattern.

Key terms: SDD frameworks, source repository, engineer as scribe, specification artifacts, translation burden, captured intent, subject matter expert, first-hand

4.1.3 Passing the baton

This section describes sequential, role-by-role specification authoring and explains why its handoffs become a collaboration bottleneck.

Key terms: Engineer as Scribe, feature branch, pull request, coding agent, specification, sequential handoffs, miniature waterfall, review overhead, shared understanding, Execution Harness

4.1.4 Mob authoring

This section explains how a team can author a specification together to eliminate handoffs, and why the approach creates scheduling and throughput constraints.

Key terms: mob authoring, mob programming, Execution Harness, mob authoring session, feature specifications, simultaneous availability, co-located team

4.1.5 Asynchronous contribution through encoded expertise

Recurring guidance from different roles can be encoded as standing context so a team can author specifications asynchronously while reserving reviews and conversations for feature-specific questions.

Key terms: standing context, Intent Harness, product specialist, architect, engineer, specification review, implementation review, feature-specific nuances

4.2 Specifying as a team

As a team begins specifying features, it separates application-wide guidance from feature-specific decisions and builds standing context without a fixed order of contributions.

Key terms: standing context, feature specifications, recurring guidance, SDD, stateless architecture

4.2.1 Product specialist defines the what

The product specialist defines feature intent in Discover conversations while building reusable standing context from product-wide rules, shared language, and recurring questions.

Key terms: business rules, standing context, destination, business vocabulary, ubiquitous language, bounded context, mandatory questions, feature specification, Discover conversation, first draft

4.2.2 Architect shapes the how

The architect establishes technical constraints and boundaries as standing context, scopes that context to avoid unnecessary agent overhead, and resolves feature-specific design questions.

Key terms: standing context, constraints, ubiquitous language, bounded contexts, interfaces, folder-level file, AGENTS.md, CLAUDE.md, cross-cutting concerns, skill

4.2.3 Engineer authors the tasks

Engineers turn product intent and architectural design into agent-executable tasks, define how those tasks will be verified, and review the plan before implementation.

Key terms: standing context, task list, original intent, acceptance tests, acceptance criteria, Test-Driven Development, unit tests, outside-in verification, checks, quality gates

4.2.4 Beyond the three roles

This section shows how specialists contribute reusable standing context and review new features to keep that context current.

Key terms: standing context, feature-specific details, security specialist, open redirect, security guidance, specification, architecture, task list, implementation

4.2.5 Standing context is grown, not installed

This section explains why teams should grow standing context from repeated experience rather than install extensive guidance upfront.

Key terms: standing context, repetition

4.3 Hands-on: building the URL shortener as a team

This section introduces a team URL-shortener exercise and describes two ways to participate.

Key terms: mob style, asynchronously, feature branch

4.3.1 Exercise Setup

This section sets up a team URL-shortener exercise in SpecKit, maps its commands to the SDD workflow, and explains choices that keep the specification authoritative and team contributions reviewable.

Key terms: SpecKit, constitution.md, Discover, Design, Execution Harness, /speckit.converge, /speckit.clarify, /speckit.checklist, /speckit.analyze, authoritative source of intent

4.3.2 First slice: each role contributes its part

The section walks through a team’s first URL-shortener feature, showing how each role adds standing context just before its artifact is drafted, then checks alignment, implements, and corrects deviations through the specification.

Key terms: standing context, constitution, specification artifact, invariants, out of scope, spec.md, /speckit.specify, /speckit.clarify, failure path, clarifications

4.3.3 Second feature: link expiration

The link-expiration example shows how established standing context reduces specification work and directs the agent’s questions toward a consequential product decision.

Key terms: standing context, constitution, module boundaries, layering, completion goals, link expiration, visitor experience, generic failure

4.3.4 Reviewing the constitution

The section distinguishes reusable architectural guidance from project-specific constitution content and shows how standing context reduced repeated human input across two features.

Key terms: constitution, reusable skill, architect’s standing context, Design conversation, standing context, first slice, second feature

4.4 Making the framework work for us

This section argues that SDD frameworks should fit a team’s existing backlog and delivery workflows so stakeholders can contribute to the Intent Harness.

Key terms: backlog tools, epics, user stories, GitHub Issues, SDD frameworks, existing workflows, Intent Harness

4.5 Summary

The chapter concludes that team-wide SDD depends on organizing contributions to specifications, growing useful standing context, and adapting the framework to existing workflows.

Concepts explained in this chapter

← Chapter 3: Keeping Specs Alive

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.