handoff

Writes a handoff document compacting the current conversation for a fresh agent session.

3|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/MaxWolf-01/agents --skill handoff-maxwolf-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/handoff
Command: npx skills add https://github.com/MaxWolf-01/agents --skill handoff-maxwolf-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent session ends or hits context limits, critical decisions, dead ends, and reasoning are lost. This Skill compacts the conversation into a structured handoff document so a fresh agent can continue the work without re-deriving context. ## Core Features & Use Cases - Purpose-scoped handoffs: Supports continuation (session ending), fork (extracting a side-quest), and return (reporting back to a parent session) modes, each with its own scoping rules. - User-confirmed mandate: Presents the inferred purpose, scope, and carry-over context to the user for confirmation before writing, keeping user decisions binding and proposals labeled. - Deduplication and sourcing: References existing artifacts (specs, tickets, ADRs, commits) by path instead of duplicating them, and ends with a Sources section marking MUST READ items. - Use Case: A long debugging session is about to hit the context limit. Invoke the handoff skill to write agent/handoffs/2024-05-01-auth-token-bug.md, then start a new session with the pickup prompt to continue seamlessly. ## Quick Start Ask the agent to create a handoff document for the next session, describing what that session should accomplish.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I continue an agent session after hitting the context limit?

Invoke the handoff skill before the session ends. It writes a handoff document to agent/handoffs/ capturing decisions, dead ends, and sources, then gives you a pickup prompt to start a fresh session that reads the file first.

What is the difference between continuation, fork, and return handoffs?

Continuation passes the full thread to the next agent when a session ends. Fork extracts only the slice relevant to a side-quest like a bug or refactor. Return reports non-obvious learnings from a detour session back to its parent.

Does the handoff document duplicate existing specs or tickets?

No. The skill references existing artifacts such as specs, tickets, ADRs, research, and commits by path or URL instead of copying their content, and ends with a Sources section explaining why each matters.

Can the agent write a handoff without my approval?

No. Before writing, the skill presents the inferred purpose, scope, and carry-over context for your confirmation. Your decisions are treated as binding input, while the agent's own proposals stay labeled as proposals.

Are API keys or personal data included in handoff files?

No. The skill explicitly redacts sensitive information such as API keys, passwords, and personally identifiable information before writing the handoff document.