handoff

Writes a compact handoff document summarizing session state, decisions, and next steps for a fresh agent session.

3|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ever-just/agentskills --skill handoff-ever-just
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/ever-just/agentskills/tree/main/skills/handoff
Command: npx skills add https://github.com/ever-just/agentskills --skill handoff-ever-just

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a long agent session ends, hits a context limit, or moves to another machine, all the in-conversation context — decisions made, work in progress, rejected alternatives — is lost, forcing the next session to re-derive everything or re-litigate settled questions. ## Core Features & Use Cases - Session State Capture: Records what is done, what is in progress, and what is explicitly outstanding so a fresh session can resume immediately. - Decision Rationale: Documents not just what was decided but why, including rejected alternatives, preventing re-litigation of settled questions. - Suggested Skills Section: Names the skills the next session should invoke, and points to existing artifacts (specs, plans, ADRs, issues) by reference instead of duplicating them. - Use Case: A debugging session is approaching the context limit mid-investigation. Invoke this skill to write a handoff to the temp directory with findings so far, the current hypothesis, and remaining steps, then start a fresh session that picks up exactly where you left off. ## Quick Start Ask the agent to write a handoff document summarizing this session so a new session can continue the work.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I continue an AI agent session in a new conversation?▼

Write a handoff document summarizing the current session's state, decisions, and outstanding work, then start a fresh session pointed at that document. The new session reads it in under a minute and resumes without replaying the whole conversation.

What should a session handoff document include?▼

Include what is done, in progress, and outstanding; decisions with their reasoning and rejected alternatives; a suggested skills section; and references to existing artifacts by path or URL. Keep it a summary, not a transcript.

Where should I save a handoff document?▼

Save it outside the repository, such as the OS temp directory or wherever scratch notes live. Never write it into tracked project files unless the user explicitly asks, since it is ephemeral working context.

When should I create a handoff without being asked?▼

Proactively suggest a handoff when a session runs long, hits a natural stopping point mid-task, or approaches a context limit. Doing it before context compaction preserves details that would otherwise be lost.

How do I avoid leaking secrets in a handoff document?▼

Redact API keys, passwords, tokens, and personally identifiable information before writing anything to disk. The handoff should reference artifacts and state, never carry credentials.