Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
adobe avatar

Session Handoff

  • 4 installs
  • 1.5k repo stars
  • Updated August 5, 2026
  • adobe/spectrum-web-components

This is a copy of session-handoff by softaworks - installs and ranking accrue to the original listing.

session-handoff is a Claude Code skill that creates and resumes handoff documents so a fresh AI agent can continue a prior session with zero ambiguity.

About

session-handoff is a Claude Code skill that creates handoff documents so a fresh AI agent can continue a previous session with full context. It has CREATE and RESUME modes, backed by Python scripts that scaffold a timestamped handoff, validate it for missing sections and secrets, list existing handoffs, and check staleness against git history. It solves long-running agent context exhaustion by capturing current state, decisions and next steps.

  • Creates handoff documents so a fresh AI agent can continue work with zero ambiguity
  • Bundles Python scripts to scaffold, validate, list and staleness-check handoffs
  • Validator blocks finalizing handoffs with detected secrets or score below 70

Session Handoff by the numbers

  • 4 all-time installs (skills.sh)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

session-handoff capabilities & compatibility

Capabilities
memory · orchestration · documentation
Use cases
memory · orchestration · documentation
From the docs

What session-handoff says it does

Creates comprehensive handoff documents that enable fresh AI agents to seamlessly continue work with zero ambiguity. Solves the long-running agent context exhaustion problem.
SKILL.md
**Do not finalize a handoff with secrets detected or score below 70.**
SKILL.md
npx skills add https://github.com/adobe/spectrum-web-components --skill session-handoff

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4
repo stars1.5k
Last updatedAugust 5, 2026
Repositoryadobe/spectrum-web-components

What it does

Create or resume a handoff document so a fresh AI agent can continue previous work with full context.

Who is it for?

Saving and resuming agent session state when context fills up or work pauses between agents

Skip if: General project documentation unrelated to agent session continuity

When should I use this skill?

The user asks to save state, create a handoff, pause work, or resume/continue previous work with a fresh agent

What you get

A validated handoff document a fresh agent can load to continue with the immediate next steps

  • Timestamped handoff markdown document in .cursor/handoffs/

By the numbers

  • 4 bundled Python scripts: create, validate, list, check_staleness
  • 4 staleness levels from FRESH to VERY_STALE

Files

SKILL.mdMarkdownGitHub ↗

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 from the project root so handoffs are created in the project's .cursor/handoffs/ directory:

cd /path/to/spectrum-web-components
python .cursor/skills/session-handoff/scripts/create_handoff.py [task-slug]

Example: python .cursor/skills/session-handoff/scripts/create_handoff.py implementing-user-auth

For continuation handoffs (linking to previous work):

python .cursor/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/.cursor/handoffs/.

The script will:

  • Create .cursor/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 for guidance.

Step 3: Validate the Handoff

Run the validation script (from project root; pass path to handoff file):

python .cursor/skills/session-handoff/scripts/validate_handoff.py .cursor/handoffs/<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.

When Python or the scripts are unavailable: (a) Create the handoff manually using 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 .cursor/handoffs/):

cd /path/to/spectrum-web-components
python .cursor/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 .cursor/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):

python .cursor/skills/session-handoff/scripts/check_staleness.py .cursor/handoffs/<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:

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 .cursor/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/

ScriptPurpose
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

Related skills

FAQ

When should I create a handoff?

When you want to save current state, pause work, or when the context window is getting full; the skill also proactively suggests one after substantial work like 5+ file edits.

Does it check for secrets?

Yes. The validator detects potential secrets and scores quality 0-100; you should not finalize a handoff with secrets detected or a score below 70.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.