Continue

Handoff Continue

Resume prior work captured by /handoff:prepare. You have zero memory of that session — the handoff file is your only context.

This skill only loads and resumes. It does not write handoffs (that is /handoff:prepare).

Resolve which handoff to load

The skill may be invoked with an optional argument ($ARGUMENTS).

1. Argument that looks like a path (contains /, or exists as a file) → use it directly as the handoff path.
2. Argument that is a bare name → substring-match it (case-insensitive) against filenames in .handoff/, falling back to the legacy dir .claude/tmp/handoff/ (pre-v1.2 handoffs). If multiple match, pick the newest by modification time. If none match, tell the user, list what is in the dirs, and stop.
3. No argument → load the newest file in .handoff/ by modification time; if that dir is missing or empty, try .claude/tmp/handoff/. If both are empty, tell the user there's no handoff to resume and stop.

Handoffs from other agents live in the same .handoff/ — resuming work prepared by a different CLI is normal. Find the newest file with a single command, e.g. ls -t .handoff/*.md (then ls -t .claude/tmp/handoff/*.md if needed).

Then

1. Read the resolved file fully with the file-reading tool.
2. Confirm which handoff loaded — one line, e.g. Resuming handoff: .handoff/20260701-143022-parkalot-cron.md.
3. Continue from its next-steps section (older handoffs may title it "Next steps"). Honor the gotchas and open questions it records before acting.

Common mistakes

• Loading a handoff but ignoring its "Caveats" / "Open questions" → repeating a mistake the previous session already hit.
• Guessing at missing context instead of reading the file fully.
• Silently picking one when several names match → say which you chose and why (newest).