Handoff
Capture operational state, not a transcript. The next agent needs facts, paths, decisions, and next actions.
When To Use
Use for:
- long-running audits;
- multi-repo publication work;
- paused implementation;
- debugging sessions with active hypotheses;
- research with source ledgers;
- job/client-search workflows;
- context compaction or thread transfer.
Handoff Contents
Include:
- objective and current status;
- repos, branches, important paths, URLs, and local servers;
- decisions made and why;
- files changed, commits, PRs, or releases;
- commands already run and their result;
- active hypotheses, blockers, or pending checks;
- suggested skills for the next session;
- exact next steps in priority order.
Closeout Receipt
When the handoff follows completed project work, include:
changed: files, commits, PRs, or artifacts that matter
verified: checks and results, or why verification was unavailable
skipped_with_reason: docs, memory, cleanup, or rules intentionally not updated
follow_up: bounded next actions only
Link to existing evidence instead of repeating it. Separate local checks from
push, CI, deployment, and public availability. Do not turn closeout into cleanup
authority: retain temporary files and old plans unless removal was approved.
Memory changes require an explicit user request; a handoff is not that request.
Compression Rules
- Link to artifacts instead of copying them.
- Do not duplicate full diffs, logs, PRDs, plans, or source docs.
- Preserve concrete dates and versions when relevant.
- Redact secrets, credentials, private contacts, and unnecessary personal data.
- Separate confirmed facts from assumptions.
Output Location
If creating a file, write it outside the project unless the user asks for an in-repo artifact. Use the OS temp directory or a clear handoff/ location approved by the repo conventions.
Final Response
Tell the user where the handoff lives, what it covers, and what the next agent should do first.
1---2name: handoff3description: Create compact handoff documents for another agent, session, or human to continue work. Use when a task is long-running, context is about to compact, work must pause, an audit needs resumable state, or the user asks for a handoff, continuation note, checkpoint, or next-session brief.4license: MIT5---67# Handoff89Capture operational state, not a transcript. The next agent needs facts, paths, decisions, and next actions.1011## When To Use1213Use for:1415- long-running audits;16- multi-repo publication work;17- paused implementation;18- debugging sessions with active hypotheses;19- research with source ledgers;20- job/client-search workflows;21- context compaction or thread transfer.2223## Handoff Contents2425Include:2627- objective and current status;28- repos, branches, important paths, URLs, and local servers;29- decisions made and why;30- files changed, commits, PRs, or releases;31- commands already run and their result;32- active hypotheses, blockers, or pending checks;33- suggested skills for the next session;34- exact next steps in priority order.3536## Closeout Receipt3738When the handoff follows completed project work, include:3940```text41changed: files, commits, PRs, or artifacts that matter42verified: checks and results, or why verification was unavailable43skipped_with_reason: docs, memory, cleanup, or rules intentionally not updated44follow_up: bounded next actions only45```4647Link to existing evidence instead of repeating it. Separate local checks from48push, CI, deployment, and public availability. Do not turn closeout into cleanup49authority: retain temporary files and old plans unless removal was approved.50Memory changes require an explicit user request; a handoff is not that request.5152## Compression Rules5354- Link to artifacts instead of copying them.55- Do not duplicate full diffs, logs, PRDs, plans, or source docs.56- Preserve concrete dates and versions when relevant.57- Redact secrets, credentials, private contacts, and unnecessary personal data.58- Separate confirmed facts from assumptions.5960## Output Location6162If creating a file, write it outside the project unless the user asks for an in-repo artifact. Use the OS temp directory or a clear `handoff/` location approved by the repo conventions.6364## Final Response6566Tell the user where the handoff lives, what it covers, and what the next agent should do first.
markoblogo