handoff

Captures session context into a durable handoff document for continuing work in a fresh session.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill handoff-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/handoff
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill handoff-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a work session ends, all conversational context is lost, forcing the next session to re-derive decisions, re-inspect repository state, and risk repeating settled debates. This Skill writes a self-contained handoff document under .marvin/handoff/ and emits a paste-ready prompt so a fresh session can resume immediately. ## Core Features & Use Cases - State-grounded capture: Inspects git branch, status, diffs, recent commits, and open PRs so every claim in the handoff traces to real repository state. - Structured handoff document: Writes a numbered, slug-named Markdown file with machine-readable YAML frontmatter (objective, branch, PR URL, spec link) plus sections for status, decisions, next steps, and open questions. - Decision preservation: Records not just what was decided but why, including rejected alternatives, so the next session does not relitigate settled choices. - Use Case: You are mid-way through a database migration on a feature branch and need to stop for the day. Run the handoff to produce .marvin/handoff/003-db-migration.md, then paste the emitted prompt into tomorrow's session to resume exactly where you left off. ## Quick Start Ask the assistant to create a handoff of the current work so you can continue it in a new session.

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?▼

Ask for a handoff and the Skill inspects your git state, writes a self-contained document to .marvin/handoff/<NNN>-<slug>.md, and prints a short prompt. Paste that prompt into the new session, which reads the file and resumes at its Next steps section.

What goes into a session handoff document?▼

The document contains YAML frontmatter (id, slug, objective, branch, PR URL, timestamp) plus sections for objective, status, repository state, key decisions with rejected alternatives, relevant files, next steps, constraints, and open questions.

Does the handoff include uncommitted changes and open PRs?▼

Yes. The Skill runs git status, git diff --stat, and gh pr view to capture uncommitted changes, recent commits, branch and base, and any open PR URL, so the handoff reflects the actual repository state rather than assumptions.

Can I update an existing handoff instead of creating a new one?▼

Yes. If a recent handoff for the same work already exists in .marvin/handoff/, the Skill offers to update it in place rather than creating a near-duplicate, keeping one handoff per work thread.

When should I not create a handoff document?▼

Skip it when the work is complete or trivially resumable from the git history alone. The handoff adds value when context lives in the conversation—decisions, rationale, and open questions—that a fresh session could not recover from the repository.