Use when starting a new session and wanting to continue from a previous handoff — reads the latest unrestored handoff document and restores session context
Resume work from a previously created handoff document. Finds the latest unrestored handoff, reads it, marks it as consumed, archives it, and sets up the session to continue from where the previous session left off.
Core principle: Read the handoff, understand the context, then continue from Next Steps.
Announce at start: "I'm using the handoff-resume skill to restore session context."
docs/handoffs/Don't use when:
PostCompact hook handles this automatically)# Look for handoff files with restored: false
ls docs/handoffs/*.md 2>/dev/nullRead each file's frontmatter and filter for restored: false. Sort by created date, newest first.
If one unrestored handoff exists: Use it automatically.
If multiple unrestored handoffs exist: Present them and ask which to resume:
Found multiple unrestored handoffs:
| # | Date | Topic | Branch |
|---|------|-------|--------|
| 1 | 2026-04-14 | handoff-skill | lg/handoff |
| 2 | 2026-04-13 | auth-refactor | fix/auth |
Which handoff should I resume from?If no unrestored handoffs exist: Check the archive:
ls docs/handoffs/_archive/*.md 2>/dev/nullIf archived handoffs exist, list them and offer to re-open one. If none exist at all, inform the user.
Read the full handoff document. Present a summary:
Resuming from handoff: <topic>
- Branch: <branch>
- Created: <date>
- Goal: <goal summary>
- Next steps: <count> items
- Files to read: <count> documentsUpdate the handoff file's frontmatter:
restored: truerestored_at: <ISO 8601 UTC timestamp>Move the file to docs/handoffs/_archive/.
git status to see if the working tree matches expectationsIf any sections contain <!-- to be enriched by LLM --> markers (from a hook-generated handoff), fill them in from available context before proceeding.
cb03f92
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.