resumelisted

# Resume Session Load a handoff document, verify it is still accurate, and resume where the previous session left off. ## Available handoffs !`ls -1t .claude/handoffs/*.md 2>/dev/null | head -10` If no handoffs are listed above, tell the user there are no handoff documents to resume from and suggest creating one with `/handoff` at the end of a session. ## Which handoff to load If arguments are provided ($ARGUMENTS), read that file from `.claude/handoffs/`. Accept either the full filename or a partial match against the files listed above. If no match is found, list the available handoffs and ask the user to specify. If no arguments are provided, read the most recent handoff (first file listed above). ## Resume process After reading the handoff document: 1. **Verify against reality** — Treat the handoff's "Current State" as a claim, not a fact. The codebase may have changed since it was written (another session, a merge, manual edits). Check for drift: - If the project is a git repository (`git status` succeeds), run `git log --oneline --since="<handoff date>"` and `git status` to see commits and uncommitted changes made after the handoff. - If it is not a git repository, compare file modification times against the handoff file instead: `find . -newer .claude/handoffs/<handoff-file> -type f -not -path "./.claude/*" -not -path "./node_modules/*" -not -path "./.git/*"` - If drift is found, flag it explicitly in the summary and prefer t