Vibe Handover Doc
Productivityvibe-handover-docVibe Handover Doc is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Generates a session continuity document at the end of a long session or when switching context on a multi-session project. Enables seamless resumption.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/context-management/handover-doc/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/vibe-handover-doc, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
vibe-handover-doc
Long sessions produce context that dies when the session ends. Capture it before it's lost.
When to Use This Skill
- End of a long development session (2+ hours of work)
- Switching context to a different project/feature
- Before taking a break on multi-session work
- When you realize "this is going to take another session"
- User says "let's continue tomorrow" or "save progress"
When NOT to Use This Skill
- Short sessions with trivial tasks
- Work that's fully committed and tested (the code IS the handover)
- When a handover doc already exists and is current
Steps
-
Capture current state:
- What branch are we on?
- What files were modified? (git status)
- Are there uncommitted changes?
- What tests are passing/failing?
-
Document completed work:
- What was accomplished this session?
- Key decisions made (reference
vibe-decision-journalentries) - Problems solved and how
-
Document remaining work:
- What's left to do?
- What's blocked and on what?
- Known issues introduced
-
Create a resume prompt:
- A specific prompt that the next session can use to get up to speed quickly
- Include: branch name, key files to read, next task to tackle
-
Save to project docs (e.g.,
docs/HANDOVER.mdordocs/handover/YYYY-MM-DD.md)
Output Format
Handover: [Feature/Project Name]
Date: [Today] Branch: [branch name]
Completed This Session
- [Task 1]
- [Task 2]
Remaining Work
- [Task 3] — [notes]
- [Task 4] — blocked by [X]
Key Decisions Made
- [Decision 1] — [rationale]
Known Issues
- [Issue 1] — [impact]
Files Changed
[git status summary]
Resume Prompt
[A specific prompt to use when resuming this work in a new session. Include context, branch, and next steps.]