Skip to main content
skill CX Codex

handoff · nicknisi — Claude Code skill: what it does, how to install

Turns a working session into a short handoff file, so a fresh agent can pick up unfinished work without rebuilding the context.

MIT ★ 114 updated 2026-08-11

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add nicknisi/claude-plugins
/plugin install essentials@nicknisi
Open on GitHub

What handoff does

The skill writes down where a session stands and what comes next, aimed at an agent that has seen none of the conversation. The file lands at a mktemp path with .md appended. Compression is the goal; a transcript is not.

Sections cover the goal, the current branch and code state, decisions already settled, approaches that failed, open questions and blockers, prioritised next steps, plus skills worth invoking later. Sections that do not fit are left out. Existing PRDs, plans, ADRs, issues, commits and diffs get referenced by path or URL instead of copied. A code block stays only when it carries context found nowhere else.

Pass a note on what the next session will handle and the whole document leans that way. Skip the argument and you get an even summary of everything. The skill asks for under 200 lines.

What it helps with

  • carry unfinished work into a new session without losing context
  • record settled decisions and their reasons
  • list abandoned approaches so the next session skips them
  • start clean once the conversation has grown long
  • collect open questions and blockers before a pause

Example prompts for the agent

  • Write a handoff document for the next session, another agent takes over from here.
  • Save the context as a handoff — the next session starts with the open questions.
  • Context is getting long, compact it into a handoff and let's start fresh.

How to install handoff

1Plugin marketplace

/plugin marketplace add nicknisi/claude-plugins
/plugin install essentials@nicknisi

This installs the whole essentials plugin with all its skills

2Skills CLI (Vercel)

npx skills add nicknisi/claude-plugins --skill handoff -a claude-code

3Manually: put the files in place

~/.claude/skills/handoff/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/handoff/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about handoff

How do I install handoff in Claude Code?

From the marketplace: run /plugin marketplace add nicknisi/claude-plugins, then /plugin install essentials@nicknisi.

What does handoff do?

It compacts the current session into a document for the next agent: the goal, what is built, decisions taken, dead ends, open questions and next steps.

What should I pass as the argument?

A short description of what the next session will focus on. The document is shaped around it.

Source text

SKILL.md · MIT
---
name: handoff
description: Compact the current conversation into a handoff document for another agent to pick up. Use when the user says "hand this off", "wrap up", "save context", "continue later", "pass this to another session", "I need to stop here", "pick this up later", or when a session is ending with unfinished work. Also use when context is getting long and the user wants to start fresh without losing progress.
argument-hint: What will the next session be used for?
---

Write a handoff document that lets a fresh agent continue this work without re-deriving any context. Save it to a path produced by `f=$(mktemp "${TMPDIR:-/tmp}handoff-XXXXXXXX") && mv "$f" "$f.md" && echo "$f.md"` (read the file before you write to it).

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

## What to capture

The goal is compression, not transcription. A good handoff is under 200 lines and gives the next agent everything it needs to start working immediately.

Include these sections (skip any that don't apply):

**Goal** — What the user is trying to accomplish, in one or two sentences. Include the "why" if it's not obvious from the task itself.

**Current state** — Where things stand right now: branch name, what's been built/changed, what works, what doesn't. Be specific — file paths, function names, test results.

**Decisions made** — Choices that were made during this session and their rationale. The next agent shouldn't re-litigate settled questions.

**What failed / dead ends** — Approaches that were tried and abandoned, and why. This prevents the next agent from repeating mistakes.

**Open questions / blockers** — Anything unresolved that needs the user's input or further investigation.

**Next steps** — Concrete actions for the next session, ordered by priority.

**Suggested skills** — Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.

## What NOT to include

Do not duplicate content already captured in other artifacts — PRDs, plans, ADRs, issues, commits, diffs. Reference them by path or URL instead. The handoff supplements the commit history; it doesn't replace it.

Do not include verbatim code blocks unless they're critical context that isn't committed anywhere (e.g., a snippet the user pasted that informed a design choice).

Do not rehash the full conversation. Distill it.

© Nick Nisi · MIT · nicknisi/claude-plugins

Similar skills

All skills for Agent setup: memory, context, orchestration →

handoff by other authors comes first.

handoff Matt Pocock Creates a handoff document from the current conversation so another agent can continue the work. Use it when a task moves to a new session or agent. CX Codex +1 1,038,491installs handoff rohitg00 handoff resumes the latest agent session for the current directory and surfaces any unanswered questions first. CX Codex +1 14,400installs handoff thedotmack Generates a structured HANDOFF.md with goals, failed attempts, and next steps. Use it when context degrades or when starting a fresh session. CX Codex +1 804installs handoff prathamdby This Claude Code skill saves project context for another session or resumes work from a handoff file. It checks current project state before picking up a task. CX Codex +1 719installs handoff ykdojo Creates or updates a HANDOFF.md file so an agent in a fresh session can pick up the task with full context. CX Codex +1 ★ 10,363repo stars resume-handoff parcadei resume-handoff reads a handoff document, checks it against the actual repo state, and suggests a way forward. Useful when a session got cut off and the context needs to come back fast. CX Codex +1 486installs vibe-handoff KhazP vibe-handoff creates a compact project handoff for another session or coding tool. It captures current work without copying chat transcripts or secrets. CX Codex +1 ★ 3,267repo stars handoff-doc Ronny (MiniMax Code team) handoff-doc is a Claude Code skill that writes a structured handover file before a session reset or task switch. It preserves critical context without relying on full chat history. CX Codex +1 ★ 741repo stars session-handoff softaworks session-handoff creates handoff documents for transferring AI agent sessions. It helps preserve progress when the context window fills up or when closing a session. ★ 2,707repo stars handoff-continue Quintin Henry (https://github.com/qdhenry/) handoff-continue writes a handoff document about the current work and starts a fresh Claude session in a Zellij pane with that document as its input. CX Codex +1 ★ 1,357repo stars design-handoff official anthropics design-handoff turns a Figma file or a written design description into a developer handoff spec: measurements, tokens, states, breakpoints, edge cases. CX Codex +1 4,000installs

From the same set18

The whole set →
image-gen image-gen is a Claude Code skill that generates or edits images with Gemini or OpenAI. It handles illustrations, diagrams, and graphics with readable labels. CX Codex +1 ★ 114repo stars squad-review squad-review runs six specialist code reviews on a branch diff, then tests every reported issue with an adversarial verifier. CX Codex +1 ★ 114repo stars socratic-tutor The socratic-tutor skill turns a code review into a guided understanding check, asking about the problem, solution, edge cases, and downstream impact. CX Codex +1 ★ 114repo stars thermo-nuclear-code-quality-review thermo-nuclear-code-quality-review conducts a ruthless maintainability audit on feature branches. Flags tangled logic, oversized files, and opportunities to cut structural bloat. CX Codex ★ 114repo stars explain-diff The explain-diff skill turns a diff, PR, branch, or commit into an HTML guide with system context, diagrams, a code walkthrough, and a quiz. Use it to understand a change or teach it to someone else. CX Codex +1 ★ 114repo stars code-simplifier code-simplifier refactors complex functions, cuts redundancy, and removes AI slop without touching public APIs or changing runtime behavior. CX Codex ★ 114repo stars git-committer The git-committer subagent reviews repository changes, runs available checks, and creates commits with semantic messages. Use it to hand off the commit workflow to Claude Code. CX Codex ★ 114repo stars tighten-prose tighten-prose strips the habits readers spot as machine-written — word clusters, inflated importance, phantom citations — and rewrites the flagged passages while keeping the author's voice. CX Codex +1 ★ 114repo stars

Project sponsors

Companies that keep this analytics open