twining-handofflisted

# Twining Handoff — Agent and Session Handoff You're transferring work to another agent, ending a session with incomplete work, or approaching context window limits. Create a handoff the next agent (or your next session) can actually continue from. > **Pattern change (#33):** the structured `twining_handoff` / `twining_acknowledge` tools are deprecated and scheduled for removal in v3. Field data across real projects showed zero calls to them, while every project that handed off well did it with rich committed markdown docs. This skill now teaches that pattern: **a committed doc + a blackboard pointer.** ## When to Invoke - When completing partial work that another agent should continue - When delegating a subtask to a specialized agent - When approaching context window limits and need to continue in a new session - When the user explicitly asks to hand off or pass work along For a session that simply finished its work, `twining_record` (Gate 2) is the handoff — don't write a doc for completed work with nothing pending. ## Workflow ### 1. Write the handoff document Create a markdown file under the project's docs or planning area (follow the project's existing convention; `docs/handoffs/YYYY-MM-DD-<topic>.md` is a good default). Include: - **State of the work** — what's done, what's in flight, what's untouched - **Next steps** — concrete, ordered, with enough context to start cold - **Decisions and constraints** — link Twining decision IDs; don't restate rationale the