handoff-golisted

Hand off the current conversation **and** start the next agent in one go: write the handoff document, then `dispatch.mjs` launches a fresh `claude` that reads it and continues. The baton leaves your hand and the next runner is already moving. You write the document (judgment). `dispatch.mjs` owns the deterministic rest — environment detection, the initial prompt, the A→B→C fallback, and shell-safe launching. ## Step 1 — Write the handoff document Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it to the OS temporary directory — not the workspace. Capture its **absolute path**. - Include a "suggested skills" section listing skills the next agent should invoke. - Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs); reference them by path or URL. - Redact sensitive information (API keys, passwords, PII). - Treat the skill arguments as a description of what the next session will focus on, and tailor the document to it. Done when: the document is saved, its absolute path is captured, secrets are redacted, and a "suggested skills" section is present. ## Step 2 — Dispatch Run the dispatcher using its **absolute path** — do NOT `cd` into the skill directory first. Always pass `--cwd` set to the **current session working directory** (the project root, not the skill directory): ``` node "<absolute path to dispatch.mjs>" --doc "<absolute doc path>" --instructions "<the