# Handoff

> 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.

- Skill: `markoblogo/handoff` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add markoblogo/handoff`
- Raw SKILL.md: https://api.skillmd.com/api/skills/markoblogo/handoff/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: MIT
- Author: markoblogo (https://skillmd.com/u/markoblogo)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/markoblogo/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:

```text
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.