Skip to content
Productivity
Skill

/session-handoff

Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".

From plugin
pro-workflow
2.9k41 skills8 agents23 commands24 hooks
Install
$ npx -y skills add rohitg00/pro-workflow --skill session-handoff --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/session-handoff

Context preview

The summary Claude sees to decide when to auto-load this skill.

Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".

SKILL.md

session-handoff.SKILL.md
name: session-handoff
description: Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".
user-invocable: true

Session Handoff

Different from wrap-up. Wrap-up is a checklist for *you*. Handoff is a document written for the *next session*.

Trigger

Use when saying "handoff", "continue later", "pass to next session", "session transfer", or ending a session and wanting to resume smoothly.

Workflow

1. Gather current state from git. 2. List completed, in-progress, and pending work. 3. Note key decisions made and their reasoning. 4. Capture any learnings from this session. 5. Generate a resume command for the next session.

Commands

git status
git diff --stat
git log --oneline -5
git branch --show-current

Output

# 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
> Continue working on [branch]. [1-2 sentence context]. Next step: [specific action].

Guardrails

  • Write for the reader (next session), not the writer.
  • Include specific file paths and line numbers where relevant.
  • The resume command should be copy-pasteable into the next session.
  • Keep it factual — describe changes functionally, don't infer motivation.
Read more
Ships withpro-workflow

Claude Code learns from your corrections: self-correcting memory that compounds over 50+ sessions. Context engineering, parallel worktrees, agent teams, and 17 battle-tested skills.

Get the whole plugin

Other skills on pro-workflow.