Skip to main content Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.
npx skills add softaworks/agent-toolkit --skill session-handoff agent-skills ai automation claude claude-code coding-agent
Handoff
Creates comprehensive handoff documents that enable fresh AI agents to seamlessly continue work with zero ambiguity. Solves the long-running agent context exhaustion problem.
Mode Selection
Determine which mode applies:
Creating a handoff? User wants to save current state, pause work, or context is getting full.
Follow: CREATE Workflow below
Resuming from a handoff? User wants to continue previous work, load context, or mentions an existing handoff.
Follow: RESUME Workflow below
Proactive suggestion? After substantial work (5+ file edits, complex debugging, major decisions), suggest:
"We've made significant progress. Consider creating a handoff document to preserve this context for future sessions. Say 'create handoff' when ready."
CREATE Workflow
Step 1: Generate Scaffold
Run the smart scaffold script to create a pre-filled handoff document:
python scripts/create_handoff.py [task-slug]
Example: python scripts/create_handoff.py implementing-user-auth
For continuation handoffs (linking to previous work):
python scripts/create_handoff.py "auth-part-2" --continues-from 2024-01-15-auth.md
Create .claude/handoffs/ directory if needed
Generate timestamped filename
Pre-fill: timestamp, project path, git branch, recent commits, modified files
Add handoff chain links if continuing from previous
Output file path for editing
Step 2: Complete the Handoff Document Open the generated file and fill in all [TODO: ...] sections. Prioritize these sections:
Current State Summary - What's happening right nowImportant Context - Critical info the next agent MUST knowImmediate Next Steps - Clear, actionable first stepsDecisions Made - Choices with rationale (not just outcomes)
Step 3: Validate the Handoff Run the validation script to check completeness and security:
python scripts/validate_handoff.py <handoff-file>
Do not finalize a handoff with secrets detected or score below 70.
Step 4: Confirm Handoff
Handoff file location
Validation score and any warnings
Summary of captured context
First action item for next session
RESUME Workflow
Step 1: Find Available Handoffs List handoffs in the current project:
python scripts/list_handoffs.py
This shows all handoffs with dates, titles, and completion status.
Step 2: Check Staleness Before loading, check how current the handoff is:
python scripts/check_staleness.py <handoff-file>
FRESH : Safe to resume - minimal changes since handoffSLIGHTLY_STALE : Review changes, then resumeSTALE : Verify context carefully before resumingVERY_STALE : Consider creating a fresh handoff
Time since handoff was created
Git commits since handoff
Files changed since handoff
Branch divergence
Missing referenced files
Step 3: Load the Handoff Read the relevant handoff document completely before taking any action.
If handoff is part of a chain (has "Continues from" link), also read the linked previous handoff for full context.
Step 4: Verify Context
Verify project directory and git branch match
Check if blockers have been resolved
Validate assumptions still hold
Review modified files for conflicts
Check environment state
Step 5: Begin Work Start with "Immediate Next Steps" item #1 from the handoff document.
Reference these sections as you work:
"Critical Files" for important locations
"Key Patterns Discovered" for conventions to follow
"Potential Gotchas" to avoid known issues
Step 6: Update or Chain Handoffs
Mark completed items in "Pending Work"
Add new discoveries to relevant sections
For long sessions: create a new handoff with --continues-from to chain them
Handoff Chaining For long-running projects, chain handoffs together to maintain context lineage:
handoff-1.md (initial work)
↓
handoff-2.md --continues-from handoff-1.md
↓
handoff-3.md --continues-from handoff-2.md
Each handoff in the chain:
Links to its predecessor
Can mark older handoffs as superseded
Provides context breadcrumbs for new agents
When resuming from a chain, read the most recent handoff first, then reference predecessors as needed.
Storage Location Handoffs are stored in: .claude/handoffs/
Naming convention: YYYY-MM-DD-HHMMSS-[slug].md
Example: 2024-01-15-143022-implementing-auth.md
Resources
scripts/ Script Purpose create_handoff.py [slug] [--continues-from <file>]Generate new handoff with smart scaffolding list_handoffs.py [path]List available handoffs in a project validate_handoff.py <file>Check completeness, quality, and security check_staleness.py <file>Assess if handoff context is still current
references/ Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Search and analyze your own session logs (older/parent conversations) using jq.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Search and analyze your own session logs (older/parent conversations) using jq.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
