Home / Lessons / Assign the work / 5 of 27

Every slice gets a takeover packet

Everything a new engineer would need to take over the work cold.

  1. The agent that finished this slice knows everything. The next one knows nothing.
  2. Before it goes, it writes four things down.
  3. The packet goes to the next agent. The first one leaves.
  4. It fills in, and picks the work up cold.

A takeover packet has four parts. The PRD and the full slice map. A setup brief with scope, decisions, dependencies and exit tests. A session-start brief: instructions ready to paste into a fresh chat. And the verified state: the real branch, commit, evidence, blockers and what still needs approval. In my setup these are four files: the PRD, the slice spec, the kickoff prompt and the state file. The kickoff prompt stays on my machine, out of git.

The lead agent writes the takeover packet for the next slice, after the work is verified. Builders and checkers send it their updates. A packet written before the work is done describes a prediction. One written after describes what is true.

How I do it

In my setup the lead agent writes the next setup brief as its last step, and it is the only one that writes the state file.

The rule

Write the takeover packet after the work is verified, and write it for someone who knows nothing.

Read next

The ideas behind it

This lesson as plain text, for your agent. Or all 27 on one page.

Try “secrets”, “merge”, “handover” or “database”.