handofflisted

Write a handoff document so a fresh agent can continue the work. Save it to the OS temp directory (`$TMPDIR` on macOS, `/tmp` on Linux) — never inside the user's project. If the user passed arguments, treat them as the focus of the next session and tailor the document accordingly. ## Modes - **End-of-session (default):** user is about to `/clear` or hand off to another machine/teammate. Produce the full template below. - **Mid-session (`mid-session` argument):** context is heavy but the work isn't done. Write the same handoff doc, then in the *current* session prune mentally — keep only the next 1–3 action items in focus, defer the rest to the doc. Don't run `/clear`; the user explicitly stayed in this session. Goal: free the agent from re-reading prior turns, not to end the session. See [`context-discipline.mini.md`](../../../standards/rules/context-discipline.mini.md) for when to reach for either mode. ## Process 1. **Locate prior artifacts.** Identify PRDs, plans, ADRs, issues, commits, and diffs that already capture parts of the work. The handoff must *reference* these by path or URL, never duplicate their content. Duplication rots fast. 2. **Pick the temp path.** Use `$(mktemp "${TMPDIR:-/tmp}/handoff-XXXXXX.md")` so two parallel handoffs don't collide. 3. **Fill the template below.** Skip sections that don't apply rather than padding with "n/a". 4. **Redact.** Strip secrets, tokens, absolute paths under `/Users/<name>` or `/home/<name>` (use `~/` or a placeholder)