← ClaudeAtlas

create-handofflisted

Synthesizes an interrogated plan (and optional relevant handoff-context) into a session-resumption handoff document at `.hivemind/handoffs/<slug>.md` that points to the plan rather than duplicating it. Pure synthesis — asks no questions. Use when the user wants to generate a session-resumption handoff, create a handoff document, write a fresh-session kickoff brief, or bridge an interrogated plan into a new session. Trigger on: "create a handoff", "generate a handoff", "session-resumption handoff", "fresh-session kickoff brief".
brenpike/hivemind · ★ 0 · AI & Automation · score 59
Install: claude install-skill brenpike/hivemind
# Create Handoff Transform an interrogated plan and any additional context which is relevant into a fresh-session kickoff handoff. This is **pure synthesis**: read the source, write the handoff, stop. Ask the user nothing — they review the written output. The handoff document should contain enough detail to bootstrap a new session with confidence, but it should point to the plan for the full rationale and details — do not duplicate them. The handoff is a **pointer document** that distills the most important context but directs the reader to the plan for the full story. Together with the plan, there must be a high-fidelity record of the interrogation and decision-making that led to the Initiative's current state. --- ## When this runs The handoff offer is **caller/human-driven**, never a prompt baked into this or any other skill. It runs when: - the user explicitly asks for a handoff, OR - the caller suggests one at a context-rich stage boundary and the user accepts. This skill never decides on its own to produce a handoff and never solicits one from inside another skill's flow. --- ## Inputs Session-agnostic and resumable at any boundary. Resolve inputs in this order: 1. **Plan (required)** — the interrogated plan. Source it from either: - the live conversation context (a plan already on screen / just produced), OR - a file at `.hivemind/plans/<slug>.md`. If both are present, prefer the live context and treat the file as a cross-check. When the plan is