session-handoff
Skill0 starsChanged 4 months agoMITView on GitHub
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.
149 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- lx-wnk/skillstheir own version, first seen Nov 16, 2026
- ingvarch/skillstheir own version, first seen Nov 16, 2026
- RMATI-11861/Claude-Skillstheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillsword for word, first seen Nov 16, 2026
- Valehead/ccBartheir own version, first seen Nov 16, 2026
- mlschodkowski/skillstheir own version, first seen Nov 16, 2026
Used with
Projects with it also use ascii-diagram, research-fleet and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SethGammonSkillascii-diagram
Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.
Also in 4 projects that use this
SethGammonSkillresearch-fleet
Parallel research using Fleet wave mechanics. Spawns multiple scout agents, each investigating a different angle of the same question. Findings are compressed between waves. Produces a unified research brief from multiple independent perspectives.
Also in 3 projects that use this
vicoa-aiSkilllive-preview
Start a local app in the current user project, expose it through a tunnel, and return preview details in structured Markdown. Use when the user asks for a preview URL, public URL, shareable localhost, mobile/web preview, or tunnel setup.
Also in 4 projects that use this
Dizzy-TenSkillbug-diagnosis
Diagnose bugs and product issues without modifying code. Use when the user explicitly invokes $bug-diagnosis or asks for diagnosis, root-cause analysis, issue classification, or fix strategy for code bugs, failing tests, configuration/dependency problems, deployment issues, performance regressions, data anomalies, or frontend/user-experience problems described through screenshots, annotations, logs, errors, or natural-language reports. Prioritize analysis and recommendations only; do not edit files.
Also in 4 projects that use this
botlearn-aiSkilldoc-gen
Also in 4 projects that use this
flyingobsidianSkillterminology
Read a codebase, find terminology, create/update definitions into a markdown document.
Also in 3 projects that use this
- +1 more from SethGammon
Other versions149 projects use a version of this.
Word for word · 2
- Ivan-propio/claude-skills★ 0100% same
- Samueladewole/claude-skills★ 0100% same
Edited · 3
- wpank/ai★ 1146% same
- christianmz565/skills★ 199% same
- nbirkner/digital-brain★ 093% same
Wrote their own version · 144
- rohitg00/pro-workflow★ 2.9ksame name
- SethGammon/Citadel★ 927same name
- wanshuiyin/HERO-Anti-OverDefense★ 805same name
- OneWave-AI/claude-skills★ 378same name
- ai-analyst-lab/ai-analyst★ 304same name
- entireio/skills★ 240same name
- Innei/SKILL★ 92same name
- yuzushi-dev/session-handoff★ 67same name
- Hive-Academy/ptah-extension★ 34same name
- Hive-Academy/PtahCode★ 34same name
134 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository121 other files it gives its agents.
- agent-md-refactorSkill
- backend-to-frontend-handoff-docsSkill
- c4-architectureSkill
- codexSkill
- command-creatorSkill
- commit-workSkill
- crafting-effective-readmesSkill
- daily-meeting-updateSkill
- database-schema-designerSkill
- datadog-cliSkill
- dependency-updaterSkill
- agency-brand-guardianSkill
- design-system-starterSkill
- agency-ui-designerSkill
- agency-ux-researcherSkill
- difficult-workplace-conversationsSkill
- domain-name-brainstormerSkill
- draw-ioSkill
- agency-ai-data-remediation-engineerSkill
- agency-ai-engineerSkill
- agency-api-platform-engineerSkill
- agency-autonomous-optimization-architectSkill
- agency-backend-architectSkill
- agency-cms-developerSkill
- agency-codebase-onboarding-engineerSkill
- agency-code-reviewerSkill
- agency-database-optimizerSkill
- agency-database-reliability-engineerSkill
- agency-data-engineerSkill
- agency-data-visualization-engineerSkill
- agency-desktop-app-engineerSkill
- agency-devops-automatorSkill
- agency-drupal-performance-engineerSkill
- agency-drupal-shopping-cart-engineerSkill
- agency-email-intelligence-engineerSkill
- agency-embedded-firmware-engineerSkill
- agency-feishu-integration-developerSkill
- agency-filament-optimization-specialistSkill
- agency-finops-engineerSkill
- agency-frontend-developerSkill
- agency-gaussdb-expert-engineerSkill
- agency-git-workflow-masterSkill
- agency-internationalization-engineerSkill
- agency-identity-access-engineerSkill
- agency-incident-response-commanderSkill
- agency-iot-fleet-engineerSkill
- agency-it-service-managerSkill
- agency-llm-post-training-engineerSkill
- agency-minimal-change-engineerSkill
- agency-mobile-app-builderSkill
- agency-mobile-release-engineerSkill
- agency-multi-agent-systems-architectSkill
- agency-network-engineerSkill
- agency-orgscript-engineerSkill
- agency-payments-billing-engineerSkill
- agency-privacy-engineerSkill
- agency-prompt-engineerSkill
- agency-rag-pipeline-engineerSkill
- agency-rapid-prototyperSkill
- agency-realtime-collaboration-engineerSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 17 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 125 edited versions we read keep these.
17
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Follow: CREATE Workflow below
- Distinctive: line 18
Follow: RESUME Workflow below
- Distinctive: line 20
Proactive suggestion?: After substantial work (5+ file edits, complex debugging, major decisions), suggest:
- Distinctive: line 27
Run the smart scaffold script to create a pre-filled handoff document:
- Very specific: line 41
Create .claude/handoffs/ directory if needed
- Distinctive: line 44
Add handoff chain links if continuing from previous
- Distinctive: line 56
Use the template structure in references/handoff-template.md for guidance.
- Distinctive: line 60
Run the validation script to check completeness and security:
- Distinctive: line 97
Before loading, check how current the handoff is:
- Distinctive: line 106
STALE: Verify context carefully before resuming
- Very specific: line 107
VERY_STALE: Consider creating a fresh handoff
- Distinctive: line 118
Read the relevant handoff document completely before taking any action.
- Distinctive: line 120
If handoff is part of a chain (has "Continues from" link), also read the linked previous handoff for full context.
- Distinctive: line 124
Follow the checklist in references/resume-checklist.md:
- Distinctive: line 126
Verify project directory and git branch match
- Distinctive: line 127
Check if blockers have been resolved
- Distinctive: line 134
Start with "Immediate Next Steps" item #1 from the handoff document.
- Distinctive: line 145
Add new discoveries to relevant sections
- Distinctive: line 165
When resuming from a chain, read the most recent handoff first, then reference predecessors as needed.
“Common” is measured: kept by at least 6 in 10 of the 125 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdThe script will:
- 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 now
- Important Context - Critical info the next agent MUST know
- Immediate Next Steps - Clear, actionable first steps
- Decisions Made - Choices with rationale (not just outcomes)
Use the template structure in references/handoff-template.md for guidance.
Step 3: Validate the Handoff
Run the validation script to check completeness and security:
python scripts/validate_handoff.py <handoff-file>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.
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 in the current project:
python scripts/list_handoffs.pyThis 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>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:
- 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
As you work:
- Mark completed items in "Pending Work"
- Add new discoveries to relevant sections
- For long sessions: create a new handoff with
--continues-fromto 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.mdEach 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/
- handoff-template.md - Complete template structure with guidance
- resume-checklist.md - Verification checklist for resuming agents
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

