home / skills / willsigmon / sigstack / session-handoff

This skill ends sessions cleanly and creates a rapid, context-rich handoff so future sessions start fast and productive.

npx playbooks add skill willsigmon/sigstack --skill session-handoff

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.7 KB
---
name: Session Handoff
description: End sessions cleanly so future sessions start fast
allowed-tools: Read, Edit, ToolSearch
model: haiku
---

# Session Handoff

End well, start fast.

## Why Handoff Matters

```
Without handoff:
→ 10 min re-explaining next session
→ Forget important context
→ Repeat mistakes

With handoff:
→ 30 sec to resume
→ Full context preserved
→ Continuous progress
```

## End of Session Protocol

### Quick Checkpoint (30 seconds)
```
"Checkpoint:
- Done: [what completed]
- WIP: [what's in progress]
- Next: [what's next]
- Blocked: [any blockers]"
```

### Full Handoff (2 minutes)
```
"Handoff summary:
1. What we accomplished
2. Current state of code
3. Pending decisions
4. Next steps in order
5. Gotchas to remember"
```

## Checkpoint Formats

### Minimal
```
"Done: Login UI
WIP: API integration
Next: Error handling"
```

### Standard
```
"Session end:
✓ Created LoginView with form
✓ Added validation logic
◐ AuthService (API calls WIP)
○ Error states
○ Tests

Next: Finish API integration
Note: Token refresh needs work"
```

### Detailed
```
"Session handoff:

## Completed
- LoginView.swift: Full UI implemented
- ValidationService.swift: Email/password rules

## In Progress
- AuthService.swift: Login call works, refresh broken
- Line 47: Need to handle 401 response

## Decisions Made
- Using Keychain for token storage
- Refresh handled client-side

## Next Session
1. Fix token refresh (see line 47)
2. Add loading states
3. Error toast component
4. Write tests

## Watch Out
- Simulator keychain quirky
- API rate limits on login endpoint"
```

## Storage Options

### Memory MCP
```
"Remember session state:
[checkpoint content]"

Auto-recalled next session.
```

### File in Project
```
# .session-state.md

Last updated: 2026-02-01

## State
[checkpoint content]

Committed or gitignored.
```

### CLAUDE.md Section
```
## Current Work
[checkpoint content]

Always loaded.
Update each session.
```

## Resume Patterns

### Quick Resume
```
Next session:
"Continue where we left off"

Claude checks:
1. Memory MCP
2. .session-state.md
3. Recent git commits
4. Last conversation
```

### Context Switch Resume
```
"Resume [project name]"

Claude loads that project's:
1. CLAUDE.md
2. Session state
3. Relevant memory
```

### Fresh Start
```
"New focus: [different area]"

Claude:
1. Parks current state
2. Loads new context
3. Clears irrelevant memory
```

## Handoff Quality Check

### Good Handoff
```
- Can resume in <1 minute
- No re-explanation needed
- Knows exactly what's next
- Remembers gotchas
```

### Bad Handoff
```
- "Where were we?"
- Re-reading old code
- Forgetting decisions
- Repeating mistakes
```

## Automatic Handoffs

### Git Commit Messages
```
Commits capture state naturally:

"WIP: Auth service, refresh TODO"

Even without explicit handoff,
commits tell the story.
```

### Memory MCP Auto-Capture
```
Configure Memory MCP to:
- Note key decisions
- Track current focus
- Remember blockers

Happens in background.
```

## Team Handoff

### Async Collaboration
```
End your session:
"Handoff for [teammate]:
[checkpoint content]"

They resume your work.
```

### PR Description
```
## Changes
[what changed]

## Testing Done
[how tested]

## Next Steps
[what remains]
```

## Anti-Patterns

### Don't
```
❌ Close without saving state
❌ Rely on memory
❌ Leave cryptic notes
❌ Skip when tired
```

### Do
```
✓ Always checkpoint
✓ Store in durable place
✓ Include the "why"
✓ Note the gotchas
```

## Quick Commands

```
"Checkpoint" → Quick state capture
"Handoff" → Full summary
"Status" → Current state
"Resume" → Continue from handoff
```

Use when: Ending any work session, switching contexts, before breaks

Overview

This skill captures and ends development sessions cleanly so future sessions start fast. It provides short checkpoints and fuller handoff summaries, plus storage and resume patterns to preserve context and decisions. Use it to avoid repeated explanations, lost work, and resumed mistakes.

How this skill works

During a session you invoke quick checkpoint or full handoff commands that record Done, WIP, Next, and Blocked items. The skill can store that state in memory, a project file (.session-state.md), or a CLAUDE.md section, and it supports automatic capture via commits or Memory MCP. On resume it checks those sources in order to reload context and next steps.

When to use it

  • Ending any focused work session to preserve momentum
  • Switching context or taking a long break
  • Before handing work to a teammate or creating a PR
  • When pausing to avoid losing decisions or gotchas
  • Automating status capture for asynchronous collaboration

Best practices

  • Keep a 30-second Quick Checkpoint for immediate capture
  • Use a 2-minute Full Handoff for complex states and decisions
  • Store handoffs in a durable place (file, CLAUDE.md, or Memory MCP)
  • Include concrete next steps in order and any gotchas to watch
  • Use descriptive git commit messages to complement handoffs

Example use cases

  • Individual developer ends a coding session with a minimal checkpoint to resume quickly later
  • Pair programming handoff noting who will finish which task and any blockers
  • Team member leaves a full handoff before PTO so the teammate can pick up work without rebriefing
  • Continuous integration of handoff notes into .session-state.md and commit history
  • Switching projects: park current state and load the new project's CLAUDE.md for a clean context switch

FAQ

How long should a Quick Checkpoint take?

About 30 seconds: list Done, WIP, Next, and any Blocked items.

Where should I store handoff notes?

Prefer durable options: Memory MCP for auto-recall, .session-state.md in the repo, or a CLAUDE.md section that loads with the project.