---
name: pause-resume
description: Two commands that carry your work across sessions. "pause" writes a handoff file capturing what you were doing, where you stopped, and the next step. "resume" reads it back so Claude picks up exactly where you left off. Triggers on "pause", "pause the session", "save where we are", "resume", "pick up where we left off", "where were we".
---

# Skill: Pause + Resume

Stop losing your place between sessions. `pause` saves the state of your work to a single handoff file. `resume` reads it back and drops you straight into flow — no re-explaining, no "where were we."

## The handoff file

One file at the root of the project you're working in:

```
SESSION-HANDOFF.md
```

It always holds the *latest* state. Each pause overwrites it (the point is "where am I right now", not a history log).

## On "pause"

Write `SESSION-HANDOFF.md` with exactly this shape. Be concrete — the next session has none of the current context except this file.

```markdown
# Session Handoff — <date/time if known>

## Goal
<The one thing we're ultimately trying to get done.>

## Done this session
- <what actually got completed, briefly>

## Current state
<Where things stand right now. What's working, what's half-built, what's broken.>

## Next step
<The single, specific next action to take on resume. Not "continue the project" — the actual next move, e.g. "wire the download buttons on the guide page to /skills/*.md and rebuild.">

## Open questions
- <anything waiting on a decision or an answer>

## Key files / places
- <paths or locations that matter, so resume doesn't have to hunt>
```

After writing it, confirm to the user in one line what you saved and that they're safe to close.

## On "resume"

1. Read `SESSION-HANDOFF.md`. If it doesn't exist, say so and ask what they want to work on.
2. Give a 3-4 line readout: the goal, where things stand, and the next step.
3. Before acting on anything the file names (a file path, a decision, a state), quickly verify it's still true — files change between sessions.
4. Then start executing from **Next step** unless the user redirects.

## Why it works

Long projects die in the gap between sessions. This closes the gap: your momentum is written down, so the next session continues instead of restarting.

## Try it

Start a multi-step task, get halfway, say "pause", close everything. Come back and say "resume" — it should tell you exactly where you left off.