handofflisted

# Handoff -- Session Context Transfer ## When to use - You are about to hit context limits and need to preserve task state - A task needs to continue in a fresh session (yours or another agent's) - Inter-agent delegation of a complex, multi-step task - User explicitly says `/handoff` or asks to "save context for later" - Before a `/checkpoint` when the task is too complex for 3-5 bullet points ## Arguments | Argument | Required | Description | |----------|----------|-------------| | `purpose` | YES | What the next session should do with this context | | `target` | no | Agent name (e.g. `target=dev2`) -- sends via inter-agent message instead of writing file | | `output` | no | File path override (default: project root `HANDOFF.md`) | Examples: - `/handoff purpose="Continue the Pipedrive connector PR review and address CI failures"` - `/handoff purpose="Finish the scheduler forceSend implementation" target=dev2` - `/handoff purpose="Debug the auth redirect loop" output=/tmp/handoff-auth.md` ## Procedure ### 1. Gather context Collect data from these sources (skip any that return empty): ```bash # Active kanban cards (assigned to current agent or recently touched). # Via the dashboard API, NOT the sqlite3 CLI: sqlite3 (and jq) are absent on a # stock Linux install -- measured on two live hosts 2026-08-04, where the CLI # call died with exit 127 while python3 was present on both. AGENT_ID="$(echo $BOT_NAME | tr '[:upper:]' '[:lower:]')" PORT="$(sed -n 's/^WEB_PORT=//p' .e