All skills
softaworks avatar

/session-handoff

@1c0662a
by softaworkssoftaworks/agent-toolkit2.5k stars
230

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.

Use this Skill: https://skilld.dev/gh/softaworks/agent-toolkit/session-handoff

This session only. Nothing lands on disk.

referencesresume-checklist.md

≈696 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Resume Checklist

Follow this checklist when resuming work from a handoff document to ensure zero-ambiguity continuation.

Pre-Resume Verification

  • Read the entire handoff document before taking any action
  • Verify you are in the correct project directory
  • Confirm the git branch matches (or understand why it might differ)
  • Check the handoff timestamp - how stale is this context?

Context Validation

  • Review "Important Context" section thoroughly
  • Understand all assumptions listed - are they still valid?
  • Check if any blockers have been resolved since handoff
  • Review "Potential Gotchas" to avoid known pitfalls

State Verification

  • Run git status to see current file state
  • Compare modified files list in handoff vs current state
  • Check if any environment variables need to be set
  • Verify any required services/processes are running

Resume Execution

  • Start with "Immediate Next Steps" item #1
  • Reference "Files Modified" table for context on recent changes
  • Apply patterns documented in "Key Patterns Discovered"
  • Follow architectural insights from "Architecture Overview"

During Work

  • Update handoff document if major new context is discovered
  • Mark completed items in "Pending Work" as you finish them
  • Add new blockers/questions as they arise
  • Consider creating a new handoff if session becomes long

Red Flags - Stop and Verify

If you encounter any of these, pause and verify context before proceeding:

  1. Files mentioned in handoff don't exist - codebase may have changed significantly
  2. Branch has diverged substantially - check git log for recent commits
  3. Assumptions are clearly invalid - reassess the approach
  4. Blockers marked as unresolved are now blocking you - escalate to user
  5. Architecture has changed - re-explore before continuing

Quick Start Commands

After reading the handoff, these commands help verify state:

# Check current branch and status
git branch --show-current
git status

# See recent commits (compare with handoff)
git log --oneline -10

# Check for any running processes mentioned
ps aux | grep [process-name]

# Verify environment
env | grep [relevant-var]

Handoff Quality Assessment

Rate the handoff quality to identify if more exploration is needed:

Aspect Good Needs Exploration
Next steps Clear, actionable Vague or missing
File references Specific paths/lines General descriptions
Decisions Rationale included Just outcomes
Context Complete picture Gaps or assumptions

If multiple aspects "Need Exploration", spend time re-exploring the codebase before continuing implementation.

Source: SKILL.md on GitHub

1 warning17d5 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    The Session Handoff skill manages markdown documents to preserve context between AI agent sessions. It uses Python scripts to collect project metadata via Git and validate document quality. Analysis identified that the skill executes local shell commands (Git) and ingests external project metadata, such as commit messages, which presents a surface for indirect prompt injection.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    4/12 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 1c0662a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Dormantupdated 9 months ago
  • session-handoff
  • context-management
  • agent-continuity
  • memory-preservation
  • long-running-tasks
  • workflow-persistence
  • handoff-documentation
  • state-capture

README badge

README badge for softaworks/agent-toolkit/session-handoff

Generates handoff documents that preserve project state, context, and pending work so fresh AI agents can resume without ambiguity. Addresses long-running sessions where context windows fill up by capturing current state, decisions made, critical files, and immediate next steps in a chainable format.

Generated from the current SKILL.md.

When should I create a handoff?
Create a handoff when the user requests to save state, pause work, or says context is getting full. Also proactively suggest one after substantial work like 5+ file edits, complex debugging, or major architecture decisions.
Can I chain handoffs together for long-running projects?
Yes. Use the `--continues-from` flag when creating a new handoff to link it to a previous one, creating a context chain that new agents can follow.
What does the validation script check for?
The validator checks for remaining TODO placeholders, required sections, potential secrets (API keys, passwords, tokens), file existence, and generates a quality score. Do not finalize a handoff with detected secrets or a score below 70.
How do I know if a handoff is still usable when resuming?
Run the staleness checker, which assesses based on time elapsed, git commits, file changes, branch divergence, and missing files. It returns FRESH, SLIGHTLY_STALE, STALE, or VERY_STALE status.
Where are handoffs stored?
Handoffs are stored in `.claude/handoffs/` with timestamped filenames like `2024-01-15-143022-implementing-auth.md`.

Generated from the current SKILL.md. These answers refresh after source changes.