agentsclimarketplace

Handing off session

Skill qte77/claude-code-plugins/plugins/cc-meta/skills/handing-off-session

A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.

Install
npx -y skills add qte77/claude-code-plugins --skill handing-off-session

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate structured session handoff notes for cross-session continuity. Use at end of session or when switching context.

SKILL.md

2.4 KB, as published. Nobody here has run it

Session Handoff

Target: $ARGUMENTS

Captures session state as a structured markdown note for the next session to pick up. Stateless — markdown files only, no database, no daemon.

Arguments

PositionNameRequiredDefaultDescription
1output-pathnoautoWhere to write the handoff note.

Default output path: .claude/handoffs/YYYY-MM-DD-<short-description>.md

The <short-description> is a 2-4 word slug derived from the session's primary focus (e.g. 2026-04-06-session-handoff-skill.md).

When to Use

  • End of a work session
  • Switching context to a different project or task
  • Before a long break
  • When context window is getting full and you want to preserve state

Workflow

  1. Scan conversation — Identify completed actions, decisions, and pending work from the current session context.

  2. Check git state — Run git diff --stat and git log --oneline -10 to capture recent changes and commits.

  3. Extract signals — Collect decisions made, alternatives rejected, blockers encountered, and open questions.

  4. Ensure output dir — Create .claude/handoffs/ if it doesn't exist.

  5. Write handoff note — Use the template below. Be concise — enough to resume, no more.

Output Template

# Session Handoff — <date>

## What Was Done
[Completed work, key commits, PRs created/merged]

## What's Pending
[Open tasks, unfinished work, next steps]

## Key Decisions
[Architectural choices, trade-offs made, rejected alternatives]

## Modified Files
[List of files changed with brief reason]

## Blockers
[External dependencies, open questions, things that need user input]

Picking Up a Handoff

Next session can read the latest handoff:

# Find latest handoff
ls -t .claude/handoffs/*.md | head -1

Or read all recent handoffs to rebuild context across multiple sessions.

Quality Check

  • Correct > Complete > Minimal (ACE-FCA)
  • ~20-50 lines output per handoff
  • Every item traces to a concrete action or artifact
  • No raw dumps — structured summaries only

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.