vibe-handover-doc
npx machina-cli add skill ash1794/vibe-engineering/handover-doc --openclawvibe-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.]
Source
git clone https://github.com/ash1794/vibe-engineering/blob/master/skills/handover-doc/SKILL.mdView on GitHub Overview
Vibe-handover-doc creates a session continuity document at the end of long sessions or when switching context on a multi-session project. It captures current state, documents completed and remaining work, and saves a ready-to-resume brief for the next session to ensure seamless project continuity.
How This Skill Works
At the end of a session, the tool prompts you to capture the current state (branch, modified files via git status, uncommitted changes, and test status). It then documents what was completed, key decisions (referencing vibe-decision-journal), and any problems solved. Next, it records what remains, blockers, and known issues, before generating a concise resume prompt for the next session. Finally, it saves the document to project docs (e.g., docs/HANDOVER.md or docs/handover/YYYY-MM-DD.md).
When to Use It
- 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"
Quick Start
- Step 1: Capture current state (branch, git status, uncommitted changes, test status)
- Step 2: Document completed work and decisions (refer to vibe-decision-journal)
- Step 3: Document remaining work and save to docs/HANDOVER.md with a resume prompt
Best Practices
- Capture current state: branch, modified files, uncommitted changes, tests status
- Document completed work: what was accomplished, key decisions referencing vibe-decision-journal
- Document remaining work: tasks left, blockers, and known issues
- Create a resume prompt tailored for the next session (branch, key files, next task)
- Save to project docs: docs/HANDOVER.md or docs/handover/YYYY-MM-DD.md
Example Use Cases
- End a 3-hour feature session and hand over to the next developer with a ready-to-read resume prompt
- Switch from feature A to bugfix work on the same project with a current handover doc
- Pause after a major refactor and save all changes, tests, and decisions for later
- Take a planned break and ensure a handover doc exists before rejoining later
- Perform a scheduled handover before a multi-day sprint starts
