handoff · rohitg00 — Claude Code command: session handoff with status
Generates a structured handoff document for passing work to another Claude session or your future self. Records status, decisions, learnings, and a resume point.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat handoff does
Running /handoff gathers your current state by pulling git status, recent commits, and modified files this session. It queries the database for errors and corrections you discovered. The result is a markdown file with sections covering what you finished, what's in progress, what's pending, key decisions made, and gotchas for next time.
The document saves to ~/.pro-workflow/handoffs/ and includes a ready-to-copy resume command. Three modes: default (all sections), --full (includes full git diff), --compact (just the resume for pasting into the next session). Unlike /wrap-up, which is a checklist for closing out properly, /handoff is meant to be read and acted on by the next session.
What it helps with
- Hand off work with full context for the next session
- Preserve key decisions and reasoning before losing focus
- Document errors and fixes discovered during this session
- Create a clean resume point without context loss
- Generate a copy-paste command to start the next session
Example prompts for the agent
- /handoff
- /handoff --compact
- /handoff --full
How to install handoff
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflow2Manually: put the files in place
.claude/commands/handoff.mdCall it with /handoff. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/handoff.mdCall it with /prompts:handoff. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/handoff.prompt.mdManually: put the files in place
.gemini/commands/handoff.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about handoff
How do I install handoff in Claude Code?
Run /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow. The /handoff command will then be available.
What does handoff do?
Creates a document containing everything needed to resume work: git status, list of changed files, key decisions, discovered learnings, and the exact point where the next session should start.
How is handoff different from wrap-up?
/wrap-up is a checklist to close a session correctly. /handoff is a document designed to be read and consumed by the next session for immediate continuation.
Source text
handoff.md · MIT
---
description: Write a session handoff with progress, decisions, and next steps.
---
# /handoff - Session Handoff Document
Generate a structured handoff document that another Claude session (or your future self) can consume immediately to continue where you left off.
## Usage
```
/handoff
/handoff --full
/handoff --compact
```
## How It Works
When the user runs `/handoff`:
1. **Gather current state**:
- Run `git status` and `git diff --stat` to see uncommitted work
- Run `git log --oneline -5` to see recent commits this session
- Check the session's edit count and corrections from the database
- List files modified this session
2. **Query learnings captured this session**:
```bash
sqlite3 ~/.pro-workflow/data.db "
SELECT category, rule, mistake, correction
FROM learnings
WHERE created_at >= datetime('now', '-4 hours')
ORDER BY created_at DESC
"
```
3. **Generate the handoff document**:
```markdown
# Session Handoff — [date] [time]
## Status
- **Branch**: feature/xyz
- **Commits this session**: 3
- **Uncommitted changes**: 2 files modified
- **Tests**: passing / failing / not run
## What's Done
- [completed task 1]
- [completed task 2]
## What's In Progress
- [current task with context on where you stopped]
- [file:line that needs attention next]
## What's Pending
- [next task that hasn't been started]
- [blocked items with reason]
## Key Decisions Made
- [decision 1 and why]
- [decision 2 and why]
## Learnings Captured
- [Category] Rule (from this session)
## Files Touched
- `path/to/file1.ts` — [what changed]
- `path/to/file2.ts` — [what changed]
## Gotchas for Next Session
- [thing that tripped you up]
- [non-obvious behavior discovered]
## Resume Command
Copy this into your next session:
> Continue working on [branch]. [1-2 sentence context]. Next step: [specific action].
```
4. **Save the handoff** to `~/.pro-workflow/handoffs/[date]-[branch].md`
## Options
- **default**: Standard handoff with all sections
- **--full**: Include full git diff in the document
- **--compact**: Just the resume command and key context (for pasting into next session)
## Why This Is Different from /wrap-up
`/wrap-up` is a checklist to close a session properly. `/handoff` is a document designed to be consumed by the next session — it's written for the reader, not the writer.
## Related Commands
- `/wrap-up` - End-of-session checklist (do this first, then handoff)
- `/replay` - Surface past learnings when starting a new session
- `/insights` - Session analytics
---
**Trigger:** Use when user says "handoff", "hand off", "pass to next session", "create handoff", "session transfer", "continue later", or when ending a session and wants to resume smoothly.
© Rohit Ghumare · MIT · rohitg00/pro-workflow
Similar slash commands
All slash commands for Agent setup: memory, context, orchestration →handoff by other authors comes first.