handoff

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.