---
name: handoff-ca1c7e4de490
description: 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.
license: MIT
metadata:
  abvx_status: experimental
  abvx_origin: adapted
---

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


---
Source attribution: markoblogo
Original project: https://github.com/markoblogo/abvx-agent-skills/blob/37a7146d940e6720a89e3281b0ddd9a0fcaf1f62/skills/handoff/SKILL.md
License: MIT
License information: https://opensource.org/license/mit
Original upstream instructions; downloaded from Mega AI Hub.

## Upstream license notice

MIT License

Copyright (c) 2026 Anton Biletskiy-Volokh

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.



# Mega AI Hub resource metadata

Creator / publisher: markoblogo
Original project: https://github.com/markoblogo/abvx-agent-skills/blob/37a7146d940e6720a89e3281b0ddd9a0fcaf1f62/skills/handoff/SKILL.md
Attribution basis: Source repository record

Fields of work: Content & Media, Operations, Project & Program Management, Sales
Roles: Business Process Analyst, Customer Success Manager, Operations Manager, Project Manager, Technical Writer
Specialties: Cross Platform
Tools: Tool not specified
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: 3dd5651f180a9750a84375d5c250e4619b5026678e6bac5496fdf3b66c9918a1