Agent skill · alirezarezvani
session-handoff
Write a handoff document so a fresh session or another agent can pick up exactly where this one left off: goal, current state, decisions, next steps and the skills to load, referencing existing files instead of copying them, with secrets redacted before saving. Use whenever the user is ending a session, switching machines, running low on context, or asks for a handoff, a handoff doc, a 'pick up where we left off' summary, or to compact the conversation for next time. Saves to a location the user picks on first run (OS temp, home folder or per-project .handoff/) and can auto-load the latest handoff at the next session start.
What it needs
About 6k tokens when loaded.
What this skill does
Handoff Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS — not the current workspace. Include a "suggested skills" section in the document, which suggests skills that the agent should invoke. Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead. Redact any sensitive information, such as API keys, passwords, or personally identifiable information. If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly. Invocation Triggers Explicit phrases (any of): "hand this off" "handoff doc" "summarize this for a new session" "compact this conversation" "I'm ending this session" "pick this up later" "wrap this up for tomorrow" "save this for the next session" Implicit signals (no phrase, but the intent is unmistakable): User announces they're switching machines or stopping for the day mid-task Conversation context is growing long without a natural stopping point User says "let me come back to this" or "I'll continue this later" When you detect an implicit trigger, propose the handoff before running it: "Want me to write a handoff for the next session?" — never run it silently. First-Run Setup On first invocation, the skill asks where to save handoffs so the project folder never gets cluttered. Setup is offered once via "Run setup now? (Y/n)" — answering N uses OS-temp defaults for this run and never re-prompts. The user can rerun setup any time via /cs-handoff-setup. See references/configuration.md for the full config field reference. Output Path The save location is read from the user's config (~/.config/handoff/config.json, or the project-local .handoff/config.json if present). When no config exists and the user declined setup, fall back to: Read the file before you write to it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/session-handoff