zap-coding-agent Handoff
Write a handoff document summarising the current conversation so a fresh agent can continue the work without losing context.
Process
- Save the document to the OS temp directory — not the current workspace
- Do not duplicate content already captured elsewhere (PRDs, ADRs, plans, commits, diffs) — reference them by path or URL
- Redact sensitive information: API keys, passwords, PII
- If the user passed arguments, treat them as a description of what the next session will focus on — tailor the document accordingly
Document Structure
# Handoff — [brief description]
## What we were doing
[1-3 sentence summary of the task and current state]
## Decisions made
[Key decisions with brief rationale — don't duplicate ADRs, just link]
## Current state
[What is done, what is in progress, what is blocked]
## Next steps
[Ordered list of what the fresh agent should do first]
## Suggested skills
[Skills the next agent should invoke — by name]
## Relevant files
[Paths or URLs to the most important artifacts]
## Open questions
[Anything unresolved that the next agent needs to address]
REQUIRED COMPANION: pocock-handoff — Matt Pocock's framing of why clean handoffs matter for multi-session work.