Skip to content
Skills Library
AI & agents · Writing

session-handoff

/session-handoff

Write a handoff file so a stuck session can resume in the other tool without losing context. Use when asked to "hand this off", "switch to Codex", "switch to Claude Code", "write a handoff", "I'm stuck, try the other tool", or when a session has burned several attempts on the same problem.

Licence
MIT
Last repository change
08.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write a handoff file so a stuck session can resume in the other tool without losing context. Use when asked to "hand this off", "switch to Codex", "switch to Claude Code", "write a handoff", "I'm stuck, try the other tool", or when a session has burned several attempts on the same problem.

Triggers from the description

hand this offswitch to Codexswitch to Claude Codewrite a handoffm stuck, try the other tool

Arguments

/session-handoff [target-tool]
Original author description

Write a handoff file so a stuck session can resume in the other tool without losing context. Use when asked to "hand this off", "switch to Codex", "switch to Claude Code", "write a handoff", "I'm stuck, try the other tool", or when a session has burned several attempts on the same problem.

How it works

  1. When to use it
  2. What to write
  3. After writing it
  4. Notes
Original SKILL.md headings · 59 lines, 651 words
SKILL.md preview
---
name: session-handoff
description: Write a handoff file so a stuck session can resume in the other tool without losing context. Use when asked to "hand this off", "switch to Codex", "switch to Claude Code", "write a handoff", "I'm stuck, try the other tool", or when a session has burned several attempts on the same problem.
argument-hint: "[target-tool]"
model: inherit
---

# Session Handoff

Capture everything the *other* tool needs to continue this task, and write it to `HANDOFF.md` in the repo root.

The receiving tool starts cold. It has none of the conversation, none of the reasoning, and no memory of what has already been ruled out. Without a handoff it re-explores ground this session already closed, and its first suggestion is usually something tried an hour ago.

Use this when switching Claude Code to Codex or back, typically because a session is stuck. A different model is genuinely useful on a stuck problem, but only if it starts from where you got to.

## When to use it

- Two or more failed attempts at the same problem, where a differently-trained model is worth trying.
- A long session about to be abandoned, whose reasoning is worth keeping.
- Work that must continue on another machine or after a restart.

Not for routine context trimming. `/compact` or a fresh session with a plan file covers that. This is specifically for crossing a tool boundary.

## What to write

Write `HANDOFF.md` with these sections. Be concrete and name real paths, commands and errors. Vagueness is what makes a handoff useless.

Write it as the first message of the next session, not as a summary for a human: address the receiving tool, open with where to start, and give instructions rather than narration. A summary describes the work; a prompt directs it. The sections below are the contents, not the voice.

### 1. Task and definition of done

One paragraph on what is being attempted, then the finish line stated so it can be objectively checked. If the goal was fuzzy in this session, say so, because the receiving tool will otherwise invent a sharper one and solve the wrong problem.

### 2. Files in play

List each file touched or read closely, with one line on **why it matters**, not just that it was opened. A bare file list is close to worthless; the reason is the context.

### 3. Decisions made, and options rejected

Both halves. The rejected options matter more than the accepted ones: they are what a cold session re-litigates first, and re-arriving at a discarded approach wastes the entire benefit of the switch. For each rejection, record the reason, not just the verdict.

### 4. Current blocker

The precise failure. Paste the actual error text, the failing command, or the observed-versus-expected behaviour. Do not summarise an error message; the wording is often the clue.

### 5. Next things to try

Ordered, most promising first. Include anything this session suspected but did not get to.

### 6. Reproduce the state

The exact commands to get from a clean checkout to the current position: branch, services to start, migrations, environment variables that must be set. If a service must be running for the failure to appear, say so. Test suites that hang because a dependency is missing look like slowness rather than failure, and cost the receiving session real time.

## After writing it

Tell the user the file is written and give them the command to open the other tool on it, for example `codex "read HANDOFF.md and continue"`. Do not switch tools yourself.

Leave `HANDOFF.md` in place rather than deleting it at the end of the task; it is a useful record of why an approach was abandoned. Add it to `.gitignore` if the repo does not want it tracked.

## Notes

- Write the file even if the session feels short. The cost is a minute; the cost of the other tool re-deriving context is much larger.
- If the user names a target tool as an argument, tailor the reproduce section to it. Codex needs `AGENTS.md` conventions called out; Claude Code needs `CLAUDE.md` ones.
- Never include secrets, tokens or `.env` contents in the handoff. Reference the variable name and where it comes from instead.

Versions

RepositoryScoreLicence
This page · model-bender/claudex-setup100MIT
iuliandita/skills100MIT
cardene777/agent-shuriken100MIT
mcorbett51090/ravenclaude100MIT
upex-galaxy/agentic-qa-boilerplate100MIT
adobe/spectrum-web-components100Apache-2.0
FrancoStino/opencode-skills-collection100MIT
h2xd/skills100MIT
davila7/claude-code-templates100MIT

Database snapshot: 13.11.2026 · package version ba583cbd2abb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90handoff
    Keep a handoff file so another coding agent (Claude Code, Codex, Kimi Code, Gemini CLI, Cursor) or a later session can continue this task without re-explaining. Use when the user asks to start, update or resume a handoff, says they will switch agents, when…
  • 100handoff
    Condense the current session into a structured handoff document so the next session or another AI continues without losing context. Use when the context is getting long, before /compact, when ending or splitting a session, when the user says "handoff" or "hand this off", or when…
  • 90handoff
    Write a handoff document so another agent or a fresh session can continue this work. Use for "handoff", "hand this off", "write a handoff", "continue this in a new session" or "pass this to another agent". For deciding whether to compact or clear, use session-budget.
  • 100handoff-writer
    把一段长会话整理成 HANDOFF.md,让新会话不读历史就能接手。 当用户说「写个交接」「hand off」「总结上下文给新会话」「收尾」, 或上下文快满了而工作还没做完时使用。 Use when the user asks to write a handoff, wrap up, or summarize context for a new session.
  • 86handoff
    Write or update a HANDOFF.md so a fresh agent can continue this work. Use when the user says "handoff", "compact this", "context is full", or "/clear and continue".
  • 100handoff
    Create a structured session handoff document for continuity across sessions. Use when ending a work session, switching contexts, or before a break. Captures decisions, progress, code changes, and next steps so a future session can pick up where you left off without losing context.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.