handoff

Generates dated handoff docs, resume prompts, and session-log metrics rows for session continuity.

2|1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/Kaidanov/grekai-skills-4all --skill handoff-kaidanov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/Kaidanov/grekai-skills-4all/tree/main/skills/handoff
Command: npx skills add https://github.com/Kaidanov/grekai-skills-4all --skill handoff-kaidanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long AI coding sessions lose all context when they end, forcing the next session to re-derive what was done, what remains, and how to verify it. This Skill captures that state once into linkable artifacts so the next session or a teammate resumes with zero re-research. ## Core Features & Use Cases - Handoff document generation: Writes a dated handoff doc with TL;DR state, proven work with commit hashes, prioritized next steps with safe approaches and proof gates, and key gotchas linked to file:line. - Standalone resume prompt: Produces a self-contained copy-paste prompt pointing to handoff, coordination, tracker, and memory paths so a fresh session continues cold. - Session metrics logging: Appends one row per session to session-log.csv with exact subagent token counts and honest n/a estimates where totals are not measurable. - Use Case: When a refactoring session is nearly out of context, say "hand off" and the Skill writes the three artifacts under docs/handoffs/, commits them, and gives you a resume prompt to paste into the next session. ## Quick Start Say "hand off" or "wrap up the session" when your context is nearly exhausted, and the Skill will write the handoff doc, resume prompt, and session-log row, then commit them.

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 AI coding session to a new session?

Invoke the handoff skill when context is nearly exhausted. It writes a dated handoff doc, a standalone resume prompt, and appends a session-log.csv row under docs/handoffs/, then commits them. Paste the resume prompt into the next session to continue.

What does a session handoff document contain?

It contains a TL;DR state, completed work with commit hashes, in-progress items, prioritized next steps with safe approaches and proof gates, rejected options, key gotchas linked to file:line, verification commands, and a session metrics block.

Can I use the handoff skill in any repository?

Yes, the skill is project-agnostic and works in any repo. Install it globally in ~/.claude/skills/handoff or project-scoped under .claude/skills/handoff, and it writes artifacts to that project's docs/handoffs/ folder.

Does the handoff skill work with concurrent sessions?

Yes, it is concurrent-safe. It appends to the shared coordination file and session-log.csv using pure appends rather than rewrites, and commits small and often so parallel sessions do not overwrite each other.

Why does the handoff doc show n/a for total tokens?

The harness does not expose per-session total tokens or wall-clock time to the model, so those fields are recorded as n/a (estimate). Exact per-subagent tokens and durations are taken from each subagent's returned usage block and never fabricated.