handoff

Writes a compact Markdown handoff document and commits it to the repository for the next session.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MarioLuppino/JobScanPlugin --skill handoff-marioluppino
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/MarioLuppino/JobScanPlugin/tree/main/.claude/skills/handoff
Command: npx skills add https://github.com/MarioLuppino/JobScanPlugin --skill handoff-marioluppino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a working session ends, all the context about open tasks, decisions, and pitfalls disappears with it. This Skill compresses the current conversation into a durable, plain-Markdown handoff file committed and pushed to the repository, so a fresh agent can resume the work without re-discovering anything. ## Core Features & Use Cases - Structured handoff template: Produces a fixed-section document (mission, state of play, open items, decisions, gotchas, suggested skills, next action) with a 400-word target and 800-word hard cap. - Durable by design: Commits and pushes the file to .claude/handoffs/<topic-slug>.md on the working branch, rewriting it in place across sessions instead of stacking new files. - Token-efficient continuity: Redacts secrets, references durable sources (commits, PRs, memory files) instead of duplicating them, and deletes the handoff when its work thread closes. - Use Case: Before ending a long debugging or release session, invoke the skill to leave a checklist the next chat can pick up with a single line: "Read .claude/handoffs/<topic-slug>.md and pick up from there." ## Quick Start Ask the assistant to write a handoff for the next session, optionally describing what that session will focus on.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off work to a new Claude Code session?▼

Invoke the handoff skill before ending the session. It writes a structured Markdown file to .claude/handoffs/, commits and pushes it, and gives you a one-line prompt the next chat can use to resume.

What should a session handoff document contain?▼

A handoff contains the mission, current state with identifiers like branch and base commit, numbered open items, settled decisions with reasoning, gotchas, suggested skills, and the single next action. Completed work is cut to one line or referenced by commit.

Where are handoff files stored in the repository?▼

Handoffs live in .claude/handoffs/<topic-slug>.md with no date in the filename. They are committed and pushed to the working branch so they survive the session container, and .claude/ never ships to plugin installers.

Can a handoff file be updated across multiple sessions?▼

Yes. The same file is rewritten in place rather than appended or duplicated, with git history preserving earlier passes. Each pass deletes finished items and re-reads state from the repository instead of memory.

When should a handoff file be deleted?▼

Delete the handoff in the commit that finishes the work it carries. A stale handoff forces every later session to read it before discovering it is worthless.