handoff

Writes an ephemeral handoff document summarizing session state for the next agent or human.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/kieranpotts/skills --skill handoff-kieranpotts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/kieranpotts/skills/tree/main/skills/handoff
Command: npx skills add https://github.com/kieranpotts/skills --skill handoff-kieranpotts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a work session ends, switches agents, or hits a context limit, all the accumulated context about what was done, what remains open, and the state of the codebase is lost. This Skill compacts that session state into a single disposable handoff document so a fresh agent or human can resume the work without repeating it or re-litigating settled decisions. ## Core Features & Use Cases - Session Compaction: Captures what was done, what is open (with named blockers), codebase state, suggested next steps, and gotchas in one structured Markdown document. - Artifact Referencing: References durable artifacts (specifications, designs, plans, issues, branches, commits) by path or URL instead of duplicating them, preventing drift. - Safe by Default: Writes outside the project tree (OS temp directory), redacts credentials and personal data, never modifies project files, and runs non-interactively for unattended workflows. - Use Case: Before ending a coding session mid-task, invoke the skill to produce a handoff document; the next morning a fresh agent reads it and continues the API integration exactly where you left off. ## Quick Start Ask the agent to hand this off to the next session, optionally naming what the next session will focus on.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I hand off an agent coding session to the next session?▼

Invoke the handoff skill with a phrase like "hand this off to the next session". The agent writes a single Markdown document covering completed work, open questions, codebase state, and next steps, then reports its absolute path.

Where is the handoff document written?▼

The document is written outside the project tree, defaulting to the OS temp directory via TMPDIR or TEMP, falling back to /tmp. This keeps the disposable file from ever being committed to the repository.

Does the handoff skill modify my project files?▼

No. Writing a handoff is strictly a reporting task; the skill must not touch code, configuration, or documentation. It only reads session context and git state, then writes one file outside the project.

Can the handoff skill run unattended without user input?▼

Yes. The skill runs non-interactively and never blocks for user input, making it safe for away-from-keyboard workflows. If it cannot determine what it needs, it stops with an error instead of asking.

When should I not use a session handoff document?▼

Do not use it to record durable lessons or decisions; those belong in the project's own artifacts like specifications or decision records. Also skip it when the session covered nothing substantive and no topic was named.