Session Handoff Agent 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".
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/rohitg00/pro-workflow --skill session-handoffThe instruction itself
6 sections, as written by the authorSession 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
- Gather current state from git.
- List completed, in-progress, and pending work.
- Note key decisions made and their reasoning.
- Capture any learnings from this session.
- 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.
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take rohitg00/session-handoff from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.