handoff

# /handoff Generates a structured handoff brief: YAML frontmatter (Obsidian-readable, vault-schema-compliant) + Obsidian-flavored markdown body containing YON-tagged structured blocks. The brief is the **work item** a fresh agent in a new session can pick up and execute autonomously. > **Structured execution spec:** [`protocol.yon`](protocol.yon). It carries the workflow steps, the verify and sources gates, and the rules as validatable records; this file is the explanation. Keep the two in sync — edit one, update the other and refresh the `@STAMP` date. ## When to use - **UC1** — Dispatch a self-contained task to a fresh agent (`agent` profile) - **UC4** — Dispatch a multi-step task that needs to be split into parallel sub-tasks (`orchestrator` profile) - **UC3** — Switch the current session to a fresh one carrying in-flight state (`new-session` profile) For UC2 (turn the *current* session into pure orchestrator mode), use [`/orchestrate-mode`](../orchestrate-mode/SKILL.md) instead — that's a behavior switch, not a handoff artifact. ## Output Each handoff produces: - **A vault file** (canonical) at `$VAULT/Handoffs/{project}/{YYYY-MM-DD}-{slug}.md` (set `$VAULT` to your Obsidian vault root) - **A chat surface** (paste-convenience): full block if file < 500 lines; otherwise summary (first 30 lines) + `📄 Full brief: <path>` For multi-handoff (`count=N`): N files + a numbered index in chat (no per-brief content in chat). The cold agent writes its retro to `Handoffs/{pr...