
Session Handoff
Create loadable handoff documents so a fresh agent session continues complex work without losing decisions, state, or task status.
Overview
Session Handoff is a journey-wide agent skill that writes comprehensive handoff documents so a solo builder can pause or swap sessions without losing project context or decisions.
Install
npx skills add https://github.com/softaworks/agent-toolkit --skill session-handoffWhat is this skill?
- Structured handoff docs for zero-ambiguity resumption by a new agent session
- Proactive triggers when context is >80% full or after major milestones (5+ file edits, architecture decisions)
- Preserves architectural decisions, completed vs pending work, and chained session links
- Supports user phrases save state, create handoff, resume from, and continue where we left off
- Proactive handoff when context window is more than 80% full
- Substantial-work trigger after 5+ file edits, complex debugging, or architecture decisions
Adoption & trust: 3.8k installs on skills.sh; 2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Long agent sessions lose context between pauses, so the next chat restarts blind and duplicates work.
Who is it for?
Solo builders on multi-session features, deep debugging, or architecture refactors who rotate agents or hit context limits.
Skip if: Single-shot tasks finished in one short chat, or teams that already use immutable tickets plus PRs as the only source of truth.
When should I use this skill?
User says save state, create handoff, load handoff, resume from, continue where we left off; or agent detects context pressure, milestones, or session end with significant progress.
What do I get? / Deliverables
A structured handoff file records status, rationale, and next steps so a fresh agent continues from the same checkpoint.
- Comprehensive handoff document with decisions, status, and next actions
- Optional chained links between related handoffs for long-running work
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Hand off half-finished API migration with schema decisions before pausing overnight.
Capture milestone status and open tasks after five-plus file edits in one sprint.
Document review fixes still pending so a new agent finishes the PR without re-reading the whole thread.
Save reproduction steps and attempted fixes mid-incident before switching to another agent.
How it compares
Structured session continuity artifact, not informal chat summaries or generic git commit messages alone.
Common Questions / FAQ
Who is session-handoff for?
Solo and indie developers using Claude Code or similar agents on projects that span many sessions and need reliable pick-up-where-you-left-off docs.
When should I use session-handoff?
Across Build while implementing and reviewing pm tasks, during Ship when debugging review feedback, and in Operate when iterating on incidents—whenever context is full, you pause, or a milestone completes.
Is session-handoff safe to install?
Handoffs may summarize code and secrets in prose; review the Security Audits panel on this page and avoid persisting credentials in handoff files.
SKILL.md
READMESKILL.md - Session Handoff
# Session Handoff Skill ## Overview The Session Handoff skill creates comprehensive handoff documents that enable fresh AI agents to seamlessly continue work with zero ambiguity. It solves the long-running agent context exhaustion problem by preserving complete context, decisions, and state across sessions. ## Purpose When working on complex, multi-session projects with AI agents, context gets lost between sessions. This skill provides a structured approach to: - **Preserve context** - Capture all critical information before context window fills - **Enable continuity** - Allow new agents to pick up exactly where you left off - **Document decisions** - Record architectural choices and their rationale - **Track progress** - Maintain clear status of completed and pending work - **Chain sessions** - Link related handoffs for long-running projects ## When to Use ### User-Triggered - User says "save state", "create handoff", "I need to pause" - User requests "load handoff", "resume from", "continue where we left off" - User mentions "context is getting full" or "save this for later" ### Agent-Triggered (Proactive) - Context window approaching capacity (>80% full) - Major task milestone completed - Work session ending with significant progress - After substantial work (5+ file edits, complex debugging, architecture decisions) - Before switching to a different task ### Resumption Scenarios - Starting a new session on an existing project - Different agent needs to continue the work - Need to recall decisions made in previous sessions - Picking up after a long break ## How It Works The skill operates in two primary modes: ### CREATE Mode Generates a comprehensive handoff document capturing current state: 1. **Generate Scaffold** - Smart script pre-fills metadata (timestamp, git status, modified files) 2. **Complete Document** - Fill in critical sections (state, context, decisions, next steps) 3. **Validate** - Automated checks for completeness, quality, and security 4. **Confirm** - Present location and summary to user ### RESUME Mode Loads and validates existing handoff documents: 1. **Find Handoffs** - List available handoffs in project 2. **Check Staleness** - Assess if context is still current 3. **Load Document** - Read handoff (and chain if linked) 4. **Verify Context** - Validate assumptions and environment 5. **Begin Work** - Start from "Immediate Next Steps" ## Key Features ### Smart Scaffolding The `create_handoff.py` script automatically captures: - Timestamp and project path - Current git branch and recent commits - Modified and unstaged files - Handoff chain links (if continuing from previous) ### Validation & Quality Assurance The `validate_handoff.py` script checks: - No incomplete `[TODO: ...]` placeholders - All required sections populated - No potential secrets (API keys, passwords, tokens) - Referenced files exist - Quality score (0-100) ### Staleness Detection The `check_staleness.py` script assesses: - Time elapsed since handoff creation - Git commits made since handoff - Files changed since handoff - Branch divergence - Missing referenced files ### Handoff Chaining For long-running projects, chain handoffs together: ``` handoff-1.md (initial work) ↓ handoff-2.md --continues-from handoff-1.md ↓ handoff-3.md --continues-from handoff-2.md ``` Each handoff links to its predecessor, providing context breadcrumbs for new agents. ## Usage Examples ### Creating a Handoff **Basic handoff creation:** ```bash python scripts/create_handoff.py implementing-user-auth ``` **Continuation handoff (linked to previous):** ```bash python scripts/create_handoff.py "auth-part-2" --continues-from 2024-01-15-auth.md ``` **Validate before finalizing:** ```bash python scripts/validate_handoff.py .claude/handoffs/2024-01-15-143022-implementing-auth.md ``` ### Resuming from a Handoff **List available handoffs:** ```bash python scripts/list_handoffs.py ``` **Check if handoff is current:** ```bash python scr