session-handoff

Installation
SKILL.md

Session Handoff

Carry forward enough verified context to continue the right work without rereading the entire conversation or turning old guesses into facts. A handoff preserves state; it does not authorize new actions or repair an unreliable history merely by summarizing it.

Prepare the Smallest Useful Handoff

Use a concise message for small work. Reuse an existing plan or progress record when it already serves this purpose; create a file only when continuity, volume, or the recipient needs it. Keep session progress out of durable skills and long-term memory.

Include only what affects continuation:

  • Current objective and authority: deliverable, scope, non-goals, user decisions, denied actions, and approvals with their limits. Distinguish a proposed approach from an accepted one.
  • Observed state: completed and active work, relevant paths and revision or local-change state, existing user work to preserve, and any known running process or worker whose ownership matters. A timed-out worker is not necessarily stopped.
  • Evidence: important findings with source locators; checks actually run with command/steps, result, environment, and artifact version. Separate source inspection, reported checks, and personal execution. Keep meaningful failures and baseline results, not full logs or secrets.
  • Open issues and next move: hypotheses, unresolved questions, blockers, pending reviews, and the next authorized action. Explain what evidence would settle a material uncertainty.

Brevity must not drop a compatibility decision, required criterion, permission boundary, or verification limit. Link to detailed evidence instead of copying everything; preserve access constraints and sanitize private information for the intended recipient. Do not upload or publish the handoff without authorization.

Correct the State Before Carrying It Forward

Installs
27
First Seen
9 days ago