handoff

Create and resume session handoffs with persistent ledger state.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/sustinbebustin/.dotfiles --skill handoff-sustinbebustin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/sustinbebustin/.dotfiles/tree/main/home/.claude/skills/handoff
Command: npx skills add https://github.com/sustinbebustin/.dotfiles --skill handoff-sustinbebustin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill ensures that your work context is preserved across sessions, even after a /clear command, preventing loss of progress and providing a smooth transition between work periods or collaborators.

Core Features & Use Cases

  • Session Continuity: Save and resume your exact working state, including goals, current tasks, and verification steps.
  • Context Management: Maintain a live ledger of your progress during long sessions, especially useful before context-heavy operations like /clear.
  • Use Case: You're working on a complex feature that spans multiple days. At the end of day one, you create a handoff. The next morning, you resume from that handoff, instantly picking up exactly where you left off, with all necessary context.

Quick Start

Use the handoff skill to create a session snapshot before ending your current work.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve AI session context before clearing the conversation?

To preserve session context before clearing, you create a handoff snapshot that saves your working state, goals, and verification steps into a persistent project database, ensuring state survives context-clearing operations.

What is the best way to resume a complex workflow across multiple days?

The best way to resume a multi-day workflow is to create a handoff at the end of a session and resume from it later, instantly restoring your exact working state, tasks, and progress from the persistent ledger.

How does state persistence work for AI session continuity?

State persistence for session continuity works by maintaining a live ledger in a project database, which stores handoff data and progress, ensuring your working state survives session restarts and clear commands.

Can I maintain a live progress ledger during long AI interactions?

Yes, you can maintain a live ledger of your progress during long sessions, which is especially useful for tracking workflow management state before context-heavy operations like clearing the conversation.

Do I need a project database to manage handoff and ledger data?

Yes, a project database is required for persistent storage of handoff and ledger data, ensuring that your session continuity and context management state survives across restarts and clear commands.

When should I create a handoff snapshot for session continuity?

You should create a handoff snapshot when ending a work period, preparing for context-clearing operations, or transitioning between collaborators, ensuring your goals and current tasks are preserved for resumption.