Skip to main content
skill CX Codex

session-handoff · sethgammon — Claude Code skill: what it does, how to install

session-handoff turns the current session into a structured HANDOFF block so the next session can pick up work without re-auditing the project.

MIT ★ 937 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add SethGammon/Citadel
/plugin install citadel@citadel-local
Open on GitHub

What session-handoff does

Triggered with /session-handoff when wrapping up a session, or run automatically by orchestrators like Archon and Fleet at session boundaries. It relies on evidence already gathered during the session — the task, changed files, verification results, decisions, blockers — and skips fresh Git inspections or directory scans when that evidence already supports a truthful summary. When a fact is uncertain or might have changed, it runs one targeted check instead of guessing.

The output is a ---HANDOFF--- block, capped at 3-5 bullets and 150 words: what changed (split into committed, uncommitted and proposed work), what was decided and why, what's still unresolved, and the next concrete step. Vague bullets like "made progress on X" are disallowed by its own quality gates.

The skill writes nothing to disk — the block is meant to be copied manually into the next session. If there's no active campaign and no Git changes, it says so plainly rather than inventing a summary.

What it helps with

  • close out a session with a clear record of what happened
  • hand off an in-progress task to another session or agent
  • log decisions along with the reasoning behind them
  • flag unresolved blockers instead of burying them in a status update
  • get a single next step instead of a full session recap

Example prompts for the agent

  • Run /session-handoff before I end this session
  • Put together a HANDOFF block for the current task
  • Summarize what changed, what we decided, and what's left before I switch sessions

How to install session-handoff

1Plugin marketplace

/plugin marketplace add SethGammon/Citadel
/plugin install citadel@citadel-local

This installs the whole citadel plugin with all its skills

2Skills CLI (Vercel)

npx skills add SethGammon/Citadel --skill session-handoff -a claude-code

3Manually: put the files in place

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

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

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

Questions about session-handoff

How do I install session-handoff in Claude Code?

Run /plugin marketplace add SethGammon/Citadel, then /plugin install citadel@citadel-local. Alternatively, run npx skills add SethGammon/Citadel --skill session-handoff -a claude-code, which places it at ~/.claude/skills/session-handoff/SKILL.md.

What does session-handoff do?

It condenses the current session into a HANDOFF block covering what changed, key decisions with their reasoning, open blockers, and the next step. It's meant to carry context into a fresh session.

How is session-handoff different from /learn or /postmortem?

session-handoff passes along context from an unfinished task to the next session. /learn pulls reusable patterns out of a finished campaign, while /postmortem writes up a structured breakdown of a failed one.

Source text

SKILL.md · MIT
---
name: session-handoff
license: MIT
description: >-
  Synthesizes the current session into a structured HANDOFF block for context
  transfer between sessions. Captures what was built, decisions made, and
  unresolved items.
user-invocable: true
auto-trigger: false
trigger_keywords:
  - handoff
  - session summary
last-updated: 2026-10-15
---

# /session-handoff — Context Transfer

## Identity

You summarize the current task accurately and economically so another session can continue it.

## Orientation

Use when ending a session and wanting to preserve context for the next one.
Also used automatically by orchestrators (Archon, Fleet) at session boundaries.

**Don't use when:** You want to extract reusable patterns from a completed campaign (use `/learn`), write a structured postmortem for a failed campaign (use `/postmortem`), or produce documentation rather than a context transfer.

## Protocol

1. **Reuse current evidence first**:
   - Start with the task, edits, verification results, decisions, and blockers already established in this session. If they are sufficient for a truthful handoff, make no tool calls.
   - Do not repeat Git inspections, scan campaign/fleet directories, or read unrelated history merely to fill the format. A handoff summarizes work; it does not start a new audit.
   - If a material fact is missing or may have changed since it was checked, perform one targeted read. Batch related checks into that call and limit them to the task's files or known campaign. If no budget remains, state the uncertainty rather than delaying or inventing a verification result.

2. **Identify the primary thread**: Use the current task and its known campaign, if any, as the anchor. Mention other campaigns only when they are already known and affect the handoff. Do not discover unrelated work to create a frame.

3. **Map data to HANDOFF fields**:
   - *What changed*: actual task output and files changed; distinguish committed, uncommitted, and proposed work when known
   - *Key decisions*: the decisions and reasons established while doing the task
   - *Unresolved items*: failed or missing verification, known blockers, and explicitly deferred work
   - *Next steps*: the next actionable step, or "none" when the task is complete

4. Output the HANDOFF block.

## Output Format

```
---HANDOFF---
- {what was built or changed — be specific}
- {key decisions and tradeoffs — include reasoning}
- {unresolved items — what's blocking}
- {next steps — what the next session should do first}
---
```

Keep it to 3-5 bullets, under 150 words. This is a context transfer, not a report.

## Quality Gates

- Every bullet must be actionable or informative
- No vague statements ("made progress on X")
- Specific file references where relevant
- Decisions include reasoning, not just the choice

## Fringe Cases

**`.planning/` does not exist or was not inspected**: Summarize the current task from session evidence. Do not inspect Git or infer campaign status merely to fill the handoff.

**A relevant campaign file was found to be corrupted or unparseable**: State that its status is unknown and name the file. Do not treat unreadable state as inactive or scan for other campaigns.

**No active campaign and no git changes**: If there is nothing to summarize, say so explicitly: "No active campaign or session changes found. Nothing to hand off." Do not fabricate a handoff.

**No context to summarize** (fresh session with no edits): Output a minimal handoff noting the session start state. At minimum, include what the user asked about and what was found.

**Campaign is in a blocked/parked state**: Include the block reason and the recommended next action in the handoff so the next session can resume immediately.

## Contextual Gates

**Reversibility:** Green — this skill writes nothing to disk; the HANDOFF block is display-only.
**Cost:** No cost actions — synthesis only; no agents spawned, no confirmation needed.
**Trust:** No gates — safe at all trust levels.

## Exit Protocol

Output the HANDOFF block and then wait for the next command. This skill does not write to disk — the HANDOFF block is the deliverable, for the user to copy into the next session or save manually.

© SethGammon · MIT · SethGammon/Citadel

Similar skills

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

session-handoff by other authors comes first.

session-handoff softaworks session-handoff creates handoff documents for AI agent session transfers. Useful when context window fills up or projects span multiple sessions. CX Codex +1 4,300installs session-handoff entireio session-handoff — a skill for Claude Code carries work context between agents and summarizes recent sessions. It activates when a task must continue in another agent. CX Codex +1 615installs session-handoff Alireza Rezvani session-handoff writes a structured handoff note with goals, open decisions, and artifact links so a fresh agent picks up right where work stopped. CX Codex +1 ★ 30,251repo stars session-handoff Rohit Ghumare session-handoff generates a structured handoff document capturing git state, open tasks, decisions, and a resume prompt for your next session. CX Codex +1 ★ 2,966repo stars handoff-engineering Alireza Rezvani handoff-engineering compacts the current session into a markdown handoff so a fresh agent can continue. References artifacts by path or URL instead of copying them. ★ 30,251repo stars handoff Rohit Ghumare Generates a structured handoff document for passing work to another Claude session or your future self. Records status, decisions, learnings, and a resume point. CX Codex +1 ★ 2,966repo 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 slicc-handoff adobe slicc-handoff hands the current task to the SLICC browser agent or asks SLICC to install a GitHub skill. Use it when the next step needs a browser session. CX Codex +1 928installs semester-handoff official anthropics semester-handoff writes a transition memo for every active case plus a cohort summary, so departing students hand their work to the incoming cohort cleanly. CX Codex +1 611installs create-handoff parcadei The create-handoff skill writes a YAML handoff document so the next agent session picks up your task without losing context. CX Codex +1 513installs

From the same set55

The whole set →
arch-reviewer arch-reviewer inspects project files for layer boundary violations, circular dependencies, and dead imports without modifying code. CX Codex ★ 937repo stars knowledge-extractor The knowledge-extractor subagent saves reusable patterns, pitfalls, and decisions from finished work for a project wiki. Run it after completing a substantial piece of work. CX Codex ★ 937repo stars verify verify — a skill to self-test the Citadel hook pipeline during a live session. Exercises real tool calls (Write, Edit, Bash, Read), verifies that hooks fire, telemetry accumulates, and no errors occur. CX Codex +1 ★ 937repo stars unharness unharness is a Claude Code skill that plans Citadel removal from a project and keeps a portable archive. It runs on requests to remove Citadel or clean up the harness. CX Codex +1 ★ 937repo stars grill grill turns a vague plan into a sharp technical spec through one-question-at-a-time interview, each with a default answer you edit. CX Codex +1 ★ 937repo stars autopilot autopilot processes queued tickets from .planning/intake/ through automated research, implementation, and verification. CX Codex +1 ★ 937repo stars doc-gen doc-gen generates function comments, directory READMEs, and API references while following the project’s existing conventions. Use it when docs should explain code behavior rather than repeat signatures. CX Codex +1 ★ 937repo stars policy-enforcer policy-enforcer is a Claude Code subagent that checks proposed actions against Citadel’s rules and returns an allow-or-block verdict. Archon and Fleet spawn it before actions with low reversibility. CX Codex ★ 937repo stars

Project sponsors

Companies that keep this analytics open