Home / Concepts

What is a takeover packet?

The documents and verified state a fresh person or agent needs to continue a piece of work.

A takeover packet has four parts: the PRD and the full slice map; a setup brief with scope, decisions, dependencies and exit tests; instructions ready to paste into a new chat; and the verified state, meaning the real branch, commit, evidence, blockers and gates. 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 it, after the previous slice is verified. Written earlier, it would describe a plan. Written after, it describes what exists.

The test for a good one is whether someone who has never seen the project could pick it up and continue without asking you anything.

Lessons that use it

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