handoff

name	handoff
description	Structured work handoff across context boundaries: triage decisions, constraints, and remaining work into a prompt-quality transfer document. Invoke whenever task involves handing off work — session restart, teammate delegation, async resumption, or any context boundary crossing.
disable-model-invocation	true

Handoff

A handoff document is a prompt — an instruction set for the receiving agent. Triage your context into a structured, information-dense transfer document that preserves high-value state and drops noise.

Mode

Two modes, determined by who receives the handoff:

• Self — receiver shares project knowledge. Task state, decisions, remaining work. Minimal codebase orientation.
• Teammate — receiver may lack project context. Adds codebase orientation, skill/tool recommendations, and convention pointers.

If the user doesn't specify, ask.

Triage

Separate your context into two categories before writing anything.

Keep — state that must survive the boundary:

• Decisions made and their rationale
• Constraints discovered during work
• External resource identifiers (URLs, issue IDs, file paths, branch names)
• Quality/verification state (what was tested, what passed/failed)
• Remaining work in priority order
• Blockers and open questions

Drop — noise in transfer:

• Intermediate exploration and search paths
• Failed approaches (unless the failure constrains remaining work)
• Content already committed to files or git history