session-handoff
Installation
SKILL.md
Session Handoff
Purpose
Write a handoff document a fresh agent — with zero memory of this session — can continue the work from. Portability is the point: new session, new harness, new directory, or a colleague.
Workflow
- Ask (or infer from the request) what the next session will be used for; tailor the document to that purpose.
- Inventory what already exists as durable artifacts — specs, plans, ADRs, issues, commits, diffs — and reference them by path or URL. Never duplicate their content unless the recipient cannot access the source.
- For another machine, harness, or colleague, verify delivery is accessible (shared URL, synced repository, or attached archive). If references are not accessible, include the full portable contents or a clearly named export and say what is missing.
- Record reference roots and repository revision (commit/hash or explicit uncommitted state), plus how relative paths resolve; do not hand off ambiguous local paths.
- Write what exists nowhere else: the current state, the decisions made in conversation and why, the exact next action, open questions, and traps already discovered.
- Include a "suggested skills" section naming which skills the next agent should invoke, so the route through the catalog survives the transition.
- Redact secrets, tokens, and personal data before writing.
- Save to the OS temporary directory (not the workspace) unless the user asked otherwise; report the absolute path.