handoff — Session Handoff
- Trigger:
/handoffor keywords "handoff", "continue this", "pass to another agent" - Best for: Long tasks split across sessions, multi-agent collaboration, context window cleanup
- Not for: Simple one-shot tasks, work that doesn't span sessions
Overview
handoff compacts the current conversation into a handoff document for another agent (or new session) to seamlessly pick up. It preserves task progress, key decisions, explored paths, and remaining work.
Trigger Conditions
handoff auto-triggers when you:
- Mention "handoff", "continue this task"
- Are approaching context window limits
- Need to transfer work to another agent
- Use the
/handoffcommand
Examples
Example 1: Continuing a Long Task
/handoff Currently implementing auth system — login and registration done, password reset remainingThe handoff document includes:
- Completed: login, registration endpoints + tests
- In progress: JWT middleware (80% done)
- Remaining: password reset, OAuth
- Key decision: using bcrypt over argon2 (and why)
- Changed file list
Example 2: Cross-Agent Collaboration
/handoff Agent A completed DB migrations and model definitions, Agent B to implement API layerExample 3: Diagnostic Handoff
/handoff Bug reproduced and narrowed to caching layer, fix not yet determined — passing to next agentHandoff Document Structure
markdown
# Handoff: [Task Name]
## Current Status
- Done / In Progress / To Do
## Key Decisions
- Decision + rationale
## Explored and Abandoned Paths
- Path + reason for abandonment
## File Changes
- Added / Modified / Deleted
## Next Steps
- Concrete, actionable tasksNotes
- Keep it concise but complete — the receiving agent should grok context fast
- Why a decision was made matters more than the decision itself
- Documenting abandoned paths prevents redundant exploration
- Handoff isn't "dumping work" — ensure the task is in a transferable state