liveBook · Manning

Handoff

As explained in Vibe Engineering

A handoff protocol is a defined procedure for transferring task state, context, and responsibility between people, agents, or execution modes.

A handoff prevents context loss when responsibility moves between agents or execution modes. An Architect may inspect dependencies, make design decisions, and reject alternatives, yet an Implementer sees none of that if the workflow passes only a mode switch or raw conversation history. The reliable protocol is a structured artifact containing conclusions rather than exploratory noise. section 5.4.2

Make the handoff artifact operational rather than narrative:

  • Record selected approaches and the reasons rejected alternatives were not used. section 5.4.2
  • List files to modify, constraints to preserve, and reference files already examined. section 5.4.2
  • Generate the document at the end of the producing session, when the agent still has complete conversation context. section 5.4.2
  • Use a repository template or an equivalent workflow convention so transitions remain repeatable and reviewable. section 5.4.2

Architecture to implementation

A useful handoff can direct an Implementer to add exponential-backoff retries and a circuit breaker to PaymentGateway, identify the implementation and test files, preserve the existing interface, retry only transient errors, and apply a five-failures-in-sixty-seconds threshold. It also records why a dependency-based and middleware-based approach were rejected.

Formalization is a tradeoff, not an automatic improvement. Small teams with simple projects may communicate more cheaply by talking, while large teams, complex systems, and regulated environments gain from consistent artifacts, reduced confusion, onboarding support, incident reduction, and audit readiness. Introduce the protocol when coordination risk exceeds its maintenance cost. section 5.5.3

How Vibe Engineering covers it

How deep it goes
Defines structured artifacts and generation workflow, but stops short of specifying a universal schema or validation mechanism.
Examples
Uses an Architect-to-Implementer document covering resilience design, files, constraints, rejected alternatives, and tests.
What it assumes
Assumes multiple agents or execution modes and teaches why raw conversation history is insufficient for transitions.
What you can do after
Apply it by generating a structured session-end artifact that lets the next agent proceed without replaying exploration.
How it connects
Connects agent roles, conversation history, context compression, repository conventions, and governance.

Also explained in

Compare how 4 books explain handoff →

Related concepts

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