# Session Handoff > 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. - Skill: `adobe/session-handoff` (Agent Skill, multi-file: 11 files) - Install (CLI): `npx skillmds@latest add adobe/session-handoff` - Raw SKILL.md: https://api.skillmd.com/api/skills/adobe/session-handoff/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: Adobe (https://skillmd.com/u/adobe) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/adobe/session-handoff --- # 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. ## Mindset You are a project manager. Context is the most perishable asset in software development. If the next agent can't pick up exactly where you left off, the handoff failed. ## 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 **from the project root** so handoffs are created in the project's `.ai/handoffs/` directory: ```bash cd /path/to/spectrum-web-components python .ai/skills/session-handoff/scripts/create_handoff.py [task-slug] ``` Example: `python .ai/skills/session-handoff/scripts/create_handoff.py implementing-user-auth` **For continuation handoffs** (linking to previous work): ```bash python .ai/skills/session-handoff/scripts/create_handoff.py "auth-part-2" --continues-from 2024-01-15-auth.md ``` The script uses the current working directory as the project path. Running from project root ensures handoffs live at `project-root/.ai/handoffs/`. The script will: - Create `.ai/handoffs/` at project root 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: 1. **Current State Summary** - What's happening right now 2. **Important Context** - Critical info the next agent MUST know 3. **Immediate Next Steps** - Clear, actionable first steps 4. **Decisions Made** - Choices with rationale (not just outcomes) Use the template structure in [references/handoff-template.md](references/handoff-template.md) for guidance. ### Step 3: Validate the Handoff Run the validation script (from project root; pass path to handoff file): ```bash python .ai/skills/session-handoff/scripts/validate_handoff.py .ai/handoffs/ ``` The validator checks: - [ ] No `[TODO: ...]` placeholders remaining - [ ] Required sections present and populated - [ ] No potential secrets detected (API keys, passwords, tokens) - [ ] Referenced files exist - [ ] Quality score (0-100) **Do not finalize a handoff with secrets detected or score below 70.** **When Python or the scripts are unavailable:** (a) Create the handoff manually using [references/handoff-template.md](references/handoff-template.md), and/or (b) output a structured handoff in chat for the user to save. ### Step 4: Confirm Handoff Report to user: - 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 (run from project root so the script finds `.ai/handoffs/`): ```bash cd /path/to/spectrum-web-components python .ai/skills/session-handoff/scripts/list_handoffs.py ``` This shows all handoffs with dates, titles, and completion status. **When Python or the scripts are unavailable:** List handoffs manually from the project root's `.ai/handoffs/` (naming: `YYYY-MM-DD-HHMMSS-[slug].md`), then load and verify context using the resume checklist. ### Step 2: Check Staleness Before loading, check how current the handoff is (from project root): ```bash python .ai/skills/session-handoff/scripts/check_staleness.py .ai/handoffs/ ``` Staleness levels: - **FRESH**: Safe to resume - minimal changes since handoff - **SLIGHTLY_STALE**: Review changes, then resume - **STALE**: Verify context carefully before resuming - **VERY_STALE**: Consider creating a fresh handoff The script checks: - 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 Follow the checklist in [references/resume-checklist.md](references/resume-checklist.md): 1. Verify project directory and git branch match 2. Check if blockers have been resolved 3. Validate assumptions still hold 4. Review modified files for conflicts 5. 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 As you work: - 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 the **project root's** `.ai/handoffs/` directory. Run the create script from project root so new handoffs go there. 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 ]` | Generate new handoff with smart scaffolding | | `list_handoffs.py [path]` | List available handoffs in a project | | `validate_handoff.py ` | Check completeness, quality, and security | | `check_staleness.py ` | Assess if handoff context is still current | ### references/ - [handoff-template.md](references/handoff-template.md) - Complete template structure with guidance - [resume-checklist.md](references/resume-checklist.md) - Verification checklist for resuming agents