Handoffs

Handoffs — Pick a saved session to resume

Browse handoff files written by /wrap-up (in ~/.claude/handoffs/) and pick one to resume. Companion to /wrap-up (the writer) and /landscape (the morning orienter).

When to use

• Starting a session and wanting to pick up a thread from a previous one.
• After /landscape flagged that recent handoffs exist for this repo.
• Searching for an older thread — ls ~/.claude/handoffs/ is grep-friendly, but this skill renders the metadata table.

Not sure whether to resume a handoff or start fresh work? That's a morning orientation call, not a handoffs call — run /landscape first. Its **Next:** line arbitrates resume-a-handoff vs /next safe from the full picture (Jira, PRs, beads, working copy). Come here once you've decided to resume a thread.

What it does

1. List handoffs across all repos, with per-repo counts.
2. Fully detail handoffs in the current repo as a pickable table, flagging which are superseded by a newer handoff, done (PR merged, all beads closed, or Jira ticket Done), or stale (branch gone / PR closed).
3. Summarise handoffs in other repos (count per repo, not full listing).
4. Optionally archive confirmed superseded, done, stale, or assisted-review handoffs to keep the picker focused.
5. Prompt you to pick one — only handoffs for the current repo are pickable.
6. On pick, render the resume block inline and surface the cd if the recorded worktree differs from pwd.

Important — what this skill cannot do

• It cannot resume for you. It surfaces the resume block; you read it and act on the next step.
• It cannot rename the session for you. On load it prints the active client's paste-ready command (§5): /name {slug} in Pi and /rename {slug} in Claude Code. Only you typing it triggers a rename.
• It cannot pick handoffs from unrelated repos. That is a deliberate guard — running commands against the wrong repo is the failure mode it prevents. To resume a handoff in an unrelated repo, cd there and run /handoffs again. Exception: repos in the same multi-repo workspace are listed and pickable (§2b/§4b), because from a workspace root they'd otherwise be invisible; picking one requires an explicit cd before any repo-scoped command runs.
• It never deletes handoff files. The opt-in archive steps (§3b–§3d) only move explicitly confirmed candidates into ~/.claude/handoffs/archive/ — they stay on disk and greppable.

Instructions

MUST use the helper script. Never construct ad-hoc ls/grep pipelines against ~/.claude/handoffs/ — they bypass the per-script permission allowlist and miss the repo-matching logic.

1. Run the helper

~/.agents/skills/handoffs/scripts/list.sh --check-branches [--stale-days N]

Forward --stale-days N when the user supplied it; otherwise use the script's 30-day default. The flag only controls the assisted §3d age-review group and never marks a row stale.

--check-branches adds branch-liveness + PR classification for current-repo handoffs. The full flag semantics, the 22-field ---HANDOFFS--- line format, and every field's meaning (supersede, branch-state, pr-state, archive-class, beads-done, deliverable-field, beads-progress, needs-review, needs-age-review) are specified once in ~/.agents/skills/handoffs/REFERENCE.md — Read it. Both /handoffs and /handoffs-tidy read off the same definitions, including §Age-review, so the two never drift on classification.

The sections you parse here: ---CURRENT-REPO--- / ---CURRENT-REPO-DISPLAY--- (identity + label, or NONE outside a repo), ---HANDOFFS--- (one row per handoff, newest first), ---SUMMARY--- (the counts, incl. current_repo_total, current_repo_superseded, current_repo_stale, current_repo_age_review, unresolved), and ---OTHER-REPOS--- ({repo-key}|{count}|{display}, count desc). The ---CURRENT-REPO-LATEST--- / ---CURRENT-REPO-LIVE--- sections are for /landscape; this skill renders the full table instead and can ignore them.

See REFERENCE §Fields for repo-identity resolution (Repo root: → cwd walk-up, origin-URL keying, .claude-symlink unification, UNRESOLVED), the supersede rules, and the branch-state / pr-state / archive-class semantics this skill renders below.

1a. Resolve Jira-Done for still-live rows (skill layer)

list.sh can read PR and bead state but cannot call the Jira MCP — so a handoff whose only "finished" signal is its ticket being closed in Jira still arrives with archive-class empty (🟢 live). Close that gap here, model-side, per REFERENCE §Jira-Done: same gate (only under --check-branches, only for still-live rows naming a ticket), same batched JQL query, same promote-to-safe rule. Skip silently if the Jira MCP errors or isn't configured.

2. Render the current-repo table

If current_repo_total > 0:

### 🧷 Handoffs — this repo ({count})

| Date | Slug | Branch | Where | Worktree | Status | Archive |
|------|------|--------|-------|----------|--------|---------|

• Date: render {date} {time} (e.g. 2026-06-03 14:32) so same-day handoffs are distinguishable at a glance. Drop the time and show just {date} when {time} is ? (neither header time nor mtime was available).
• Slug: from the filename (e.g. ab-1107-cta-event).
• Branch: from the parsed line; ? if unknown.
• Where: basename of the recorded cwd. Append (current) if it matches pwd. Special cases: empty cwd → —; cwd ending in / → use the next-up segment, e.g. worktrees/ → (worktrees root).
• Worktree: ✅ if exists=Y; ✂️ (icon only, no word) if exists=N. The ✂️ reads as "pruned" and the footnote legend below spells it out; everything in the current-repo table is pickable by definition (handoffs that couldn't be matched to a repo never reach this table), so no separate Pickable column.
  • Emit emoji glyphs exactly as written here, including the variation selector on ✂️ and ⚠️ (the wide colored forms, not the narrow text ✂︎/⚠︎). Mixing the two presentations across rows makes column widths jump — keep one form so the cells line up.
• Status: classify the row per REFERENCE §Status (the 9-step precedence: supersede → open PR → merged PR → beads-done → Jira-Done → closed PR → merged → gone → live). Emit the glyphs exactly as written there.
• Archive: render the candidate flag per REFERENCE §Archive-glyph — safe → 🗄️ safe, keep → ⚠️ keep?, empty → — (a §1a Jira-Done promotion counts as safe).

If current_repo_total == 0 and CURRENT-REPO != NONE: _No handoffs for this repo ({CURRENT-REPO-DISPLAY})._

If CURRENT-REPO == NONE: _Not in a git repo — handoffs cannot be matched to a current repo. Showing global counts only._

Render this section exactly once, in this position. Do not repeat the "No handoffs for this repo" sentence later (e.g. after §3's other-repos table) — once is enough. If current_repo_total == 0 but other repos exist, the next section's table provides the rest of the context.

2b. 🧱 Render the workspace-members table

Skip this section entirely when workspace_member_handoffs == 0.

In a multi-repo workspace the root aggregates independent member repos, so handoffs recorded in a member key to the member — not the root. Without this section they'd sit in §3's other-repos summary as a bare count, unpickable from the directory you orient in. See REFERENCE §Workspace-members.

Render from ---WORKSPACE-MEMBER-HANDOFFS--- (24 fields: the usual 22 plus {member-display}|{member-path}):

### 🧱 Handoffs — workspace members ({workspace_member_handoffs})

| Date | Repo | Slug | Branch | Worktree | Status | Archive |
|------|------|------|--------|----------|--------|---------|

• Same column semantics as §2, plus Repo = {member-display}.
• Status and Archive: classify exactly as §2 (REFERENCE §Status / §Archive-glyph). Member rows are classified against their own repo, so ✅ PR merged / ⚪ branch gone are meaningful here.
• Sort newest-first (the emitted order); group visually by repo only if it aids scanning.
• Cap at 10 rows. When more exist, render the 10 newest and add _+{N − 10} more — cdinto the member repo and run/handoffs for its full list._
• When workspace_classified == 0 (ran without --check-branches), add: _Status unclassified — member liveness needs --check-branches._

Then subtract these repos from §3's other-repos table so the same handoffs aren't counted twice — a member repo listed here must not also appear as an "other repo".

Member rows are listed and pickable here but never archived here — §3b's archive flow stays strictly current-repo. Tidying members is /handoffs-tidy's job (REFERENCE §Archive-flow-members). When members hold archivable rows, say so once under this table: _{N} member handoff(s) look finished — /handoffs-tidy to archive them._

3. Render the other-repos summary

If other_repos > 0:

### 🗂️ Handoffs — other repos ({other_repos})

| Repo | Handoffs |
|------|----------|

• Repo: use the {display} field from each ---OTHER-REPOS--- line (the script has already stripped .git and taken the basename).
• Rows already arrive sorted by count desc — render in that order.
• Do not list individual files — that's the point of "summarise."

Otherwise skip the whole section.

If unresolved > 0, surface them. When unresolved ≤ 5, list each one by filename so the user can cat it directly — a bare count is unactionable. When unresolved > 5, fall back to a count footnote to avoid clutter.

unresolved ≤ 5:

_⚠️ {unresolved} handoff(s) could not be matched to any repo (recorded path is invalid or its parent tree is gone):_
- `~/.claude/handoffs/{filename}`
- `~/.claude/handoffs/{filename}`

Pull the filenames straight from the ---HANDOFFS--- section where repo-key=UNRESOLVED. Render in the same newest-first order the script emits.

unresolved > 5:

_⚠️ {unresolved} handoff(s) could not be matched to any repo (recorded path is invalid or its parent tree is gone). Run `grep -L "Repo root:" ~/.claude/handoffs/*.md` to find them._

Do not add a global pruned-count footnote. The Worktree column in the current-repo table already makes pruning visible per-row. Add a one-time pickability hint immediately under the current-repo table (when current_repo_pruned > 0):

_✂️ = original worktree was pruned (no longer exists); still pickable — you'll resume in your current checkout or a fresh worktree._

This is a tooltip-style explainer keyed to the column legend, not a count. Skip it when current_repo_pruned == 0.

3b. 🗂️ Archive cleanup candidates (opt-in)

Run the archive flow exactly as REFERENCE §Archive-flow specifies: skip only if current_repo_superseded == 0, current_repo_stale == 0, and §1a produced no Jira-Done promotions; otherwise present the effective candidates in the three regret-ordered groups (Superseded / Done / Stale), prompt with AskUserQuestion (multiSelect, labelled and described per that section), archive the selected filenames in one archive.sh call, and parse ---ARCHIVED--- / ---SKIPPED---. Never offer a 🟢 live, 🟠 PR open, or unknown row; archive.sh only moves, never deletes.

When the flow says to drop archived rows from "any subsequent listing or picker", that is this skill's current-repo table and §4 picker — remove the archived rows and subtract them from current_repo_total so §4 doesn't offer them. If the user selects none, render nothing and continue to §4.

(/handoffs-tidy is the standalone twin of this step: same flow, no table or picker around it.)

3c. 🔍 Trunk handoffs worth a look (opt-in)

If any current-repo row has needs-review=Y, run the assisted prompt per REFERENCE §Trunk-review after §3b — a separate, clearly-labelled prompt for legacy trunk-parked handoffs the script couldn't auto-classify (partial bead closure, no **Deliverable:** marker). Drop any the user archives from the table and §4 picker, same as §3b. Skip the step entirely when no row is flagged.

3d. 🕰️ Old handoffs with no completion signal (opt-in)

If any current-repo row still has needs-age-review=Y after §1a Jira-Done promotion, run the assisted prompt exactly as REFERENCE §Age-review specifies. This is a separate, clearly-labelled judgement group for old, trunk-parked rows with no usable PR signal or resolvable beads. Age is not a done signal: leave every option unselected, archive only explicit choices, and never fold these rows into §3b's automatic candidate classes. Drop confirmed archives from the table and picker as in §3b. Skip entirely when no row is flagged.

4. Pick a handoff (current repo only)

If current_repo_total == 0, skip this step.

If current_repo_total is between 1 and 4, use AskUserQuestion:

• Option label: {date} {slug} (truncate slug if needed to stay under the chip width).
• Option description: {time} · Branch: {branch} | Where: {basename of cwd} (lead with the HH:MM so several same-day handoffs are distinguishable here; omit the {time} · prefix when {time} is ?).

If current_repo_total > 4, do not force the picker (the option cap is 4). Instead, print:

**Pick one to load:** reply with the slug or filename (e.g. `ab-1344-login-state-decision` or `2026-05-21-ab-1344-login-state-decision.md`).

Only pickable rows (✅) are valid choices. Pruned-worktree handoffs are pickable — they just resume in a different checkout. If the user picks an unresolved one, point them at cat ~/.claude/handoffs/{filename} for read-only access.

4b. Picking a workspace-member handoff

Member rows (§2b) are pickable, but only with an explicit directory change — the wrong-repo guard is honoured by making the cd mandatory, not by hiding the handoff.

When workspace_member_handoffs > 0, extend the §4 prompt (or the "reply with the slug" line) to cover member rows too, labelling them {date} {repo}/{slug} so they're distinguishable from current-repo rows.

On picking a member handoff, render the resume block per §5, then lead with the switch:

⚠️ **This handoff belongs to `{member-display}`, not the repo you're in.**
**Switch first:** `cd {member-path}`

Everything in the resume block below — branches, beads, commands — refers to that repo.

Do not run repo-scoped commands (worktree creation, git checkout, bd) for a member handoff from the current directory; the §5 exists=N worktree flow assumes you're inside the handoff's own repo, so defer it until the user has switched. Re-running /handoffs from {member-path} gives the full current-repo experience for that repo, including the archive flow.

5. Load the picked handoff

Use the Read tool on the absolute path {HANDOFFS-DIR}/{filename}.

Render the file content verbatim inside a fenced block so the rest of the session treats it as resume context:

### 📥 Loaded: `{filename}`

```markdown
{file contents}
```

Then surface a paste-ready rename so the resumed session is legible in the session list. Derive the slug from the filename (strip the YYYY-MM-DD- prefix and .md suffix):

**Rename this session to match:**

/name {slug}

(Paste it into Pi's command input and press Enter. In Claude Code, use `/rename {slug}` instead.)

Skip the rename line only if the current session is already named for this slug.

Then offer the right follow-up based on exists:

exists=Y — worktree still on disk

If recorded cwd differs from pwd:

**Switch directory:** `cd {cwd}` _(handoff was recorded in a different worktree of this repo)_

If recorded cwd matches pwd: no extra note.

(Don't run cd yourself — shell state doesn't persist across Bash calls.)

exists=N — worktree was pruned

First, check whether this handoff is superseded. If the picked row's superseded-by field is non-empty, a newer handoff already continues this thread (same branch, topic, or same-day re-wrap — see supersede-reason). Look up that newer row by filename; if it has exists=Y, the work likely moved to a live worktree — surface it as the recommended option before asking about recreation:

Original worktree {cwd} is gone. A newer handoff {newer-slug} ({humanised reason}) continues this thread in {newer-where} (still on disk). What would you like to do?

Options (use AskUserQuestion):

• Load the newer handoff instead — Open {newer-filename} from {newer-where} (recommended). Treat as if the user had picked that filename in §4 — go back to the top of §5 with the new file.
• Recreate this worktree — proceed with the regular worktree-creation flow below.
• Resume here — stay in the current checkout.

If superseded-by is empty (or the newer handoff is itself pruned, exists=N), skip this prompt.

Second, assess this checkout as a landing spot. The original worktree is gone, so you'll resume either here (the current checkout) or in a fresh worktree. Gather the facts in one call:

git rev-parse --abbrev-ref HEAD && git status --porcelain && git branch --list "{branch}"

Read four signals from the output:

• on-branch — HEAD (line 1) already equals {branch}.
• clean — git status --porcelain printed nothing (no uncommitted work to disrupt by switching branches).
• branch-exists-locally — git branch --list printed a line for {branch}.
• fresh worktree — HEAD matches worktree-*, the auto-generated name claude - gives a throwaway worktree. This is the strong signal that the user spun up this checkout specifically to host the resume.

Then branch on them:

on-branch → already on a viable spot. Render and skip to §6, no prompt:

**Already on `{branch}` here** (`{pwd}`). No worktree action needed — resume from this checkout.

clean + fresh worktree (the claude - case) → the user opened this worktree for this handoff, so adopting the branch in place is the whole point — don't push a nested worktree. The adopt command depends on branch-exists-locally:

• missing → git checkout -b {branch} (create it here — the usual case when wrap-up predated the branch or it was deleted).
• exists → git checkout {branch}.

Ask via AskUserQuestion:

Original worktree {cwd} is gone, but {pwd} looks like a fresh worktree ({HEAD}) you opened to resume here. Adopt {branch} in this checkout?

Options:

• Adopt here (recommended) — runs git checkout -b {branch} (or git checkout {branch} if it already exists). No second worktree.
• Separate worktree — fall through to the worktree-creation flow below.
• Stay as-is — leave the branch alone; just resume reading from here.

On Adopt here, run the adopt command. On success render and skip to §6:

✅ Now on `{branch}` in `{pwd}`. Resume from this checkout.

If it fails (e.g. the branch is checked out in another live worktree), surface the stderr and offer the Separate worktree flow instead.

otherwise (dirty tree, or a real branch you'd disrupt by switching) → adopting in place would clobber existing work, so offer a fresh worktree. Fall through to the worktree-creation flow below.

---

Offer to recreate the worktree. Compute the proposed values:

• {worktree-path} = the recorded cwd if its parent directory still exists on disk; otherwise {pwd}/../worktrees/{basename of recorded cwd}. If the basename is empty or generic (worktrees, .), use {topic-slug} from the filename instead.
• {branch} = the branch parsed from the handoff (Branch column).
• The git worktree add form depends on branch-exists-locally (from the assessment above): an existing branch is checked out into the new worktree (git worktree add {path} {branch}); a missing branch must be created with it (git worktree add -b {branch} {path}). Plain git worktree add {path} {missing-branch} errors — that's the failure to avoid.

Ask via AskUserQuestion:

Original worktree {cwd} is gone. Recreate it?

Options:

• Create worktree — runs the git worktree add form matching the branch's existence (see above) in the current repo.
• Resume here — stay in the current checkout ({pwd}); user can adopt the branch themselves (git checkout -b {branch} if it doesn't exist yet, else git checkout {branch}).
• Show command — prints the git worktree add invocation without running.

On Create worktree, pick the form by branch-exists-locally:

git worktree add "{worktree-path}" "{branch}"        # branch exists locally — check it out
git worktree add -b "{branch}" "{worktree-path}"     # branch missing locally — create it with the worktree

If the command succeeds, render:

✅ Worktree created at `{worktree-path}`.

**Switch directory:** `cd {worktree-path}`

If it fails (path already exists, dirty index, …), surface the stderr and fall back to Show command behaviour. Do not retry, do not delete anything, do not --force.

On Resume here:

**Resuming in current checkout** (`{pwd}`). If you need the branch, run `git checkout -b {branch}` (or `git checkout {branch}` if it already exists) — the pruned worktree's commits are still in the repo.

On Show command, print both forms and say which to run:

**Worktree pruned.** Original location `{cwd}` no longer exists. To recreate it yourself:

```bash
git worktree add -b {branch} {worktree-path}   # if {branch} doesn't exist locally yet — create it
git worktree add {worktree-path} {branch}      # if {branch} already exists — check it out

### 6. Footer

```markdown
---
**Next:** act on the resume block's *Suggested next step*. Run `/landscape` for a fresh orientation if more than a day has passed since the handoff was written.

Failure modes

Each step is independent — a failure in one should not block the others.

• ~/.claude/handoffs/ missing: render _No handoffs directory yet. Run /wrap-up at the end of a session to create one._ and stop.
• Empty directory: render _No handoffs saved yet._ and stop.
• Not in a git repo: render the other-repos summary (everything is "other"); skip the pickable table and step 4.
• Picked handoff is unreadable: report the path and suggest cat — don't fabricate content.
• Offline / remote unreachable (git ls-remote fails or times out): branch-state degrades to local-only — merged is still detected against the local default tip, but branches with no local ref report unknown rather than a false gone. The skill keeps working; the stale group in §3b just shrinks. Don't retry the network call.
• gh missing, unauthenticated, or timed out: PR detection degrades — every pr-state reports unknown and the Status/Archive columns fall back to branch-state, plus beads-done (which is local and unaffected). No error, no retry. The cost: squash-merged branches reappear as ⚪ branch gone (keep?) rather than ✅ merged (safe), unless a closed bead or §1a Jira-Done still marks them done.
• bd missing or no .beads/: beads-done is always empty — no error. Finished work then relies on PR/branch/supersede (and §1a Jira) signals alone.
• Jira MCP missing or errors: §1a is skipped silently; PR/bead/supersede classification stands. A handoff whose only finished signal was a closed ticket will show 🟢 live — acceptable degradation, never a failure.

Notes

• Handoffs are written by /wrap-up. If a session ends without /wrap-up, there is nothing here to recover. That's intentional — the index lists /wrap-up next to /handoffs for a reason.
• File naming convention: ~/.claude/handoffs/YYYY-MM-DD-{slug}.md. Collision suffixes from wrap-up (-2, -3, …) are preserved as part of the slug.
• Picking a handoff does not clean it up. Old handoffs accumulate by design — they're cheap and grep-friendly. The §3b archive step only offers superseded, done, or stale rows (and only on request); §3d separately offers sufficiently old signal-less rows for explicit judgement. Neither flow touches live/open-PR work automatically, and neither sweeps anything by itself.
• "Done" detection has three independent sources, each ground truth in its own domain: a merged PR (matched by branch or by a number recorded in the body — the latter rescues trunk-parked handoffs that recorded main), all referenced beads closed (local bd, works even on trunk repos with no PR), and a Jira ticket in the Done category (§1a, skill-resolved). Any one is enough; together they cover the cases — trunk-based completion, post-merge wrap-ups on main, ticket-only closure — that the old branch/PR-only check reported as 🟢 live.
• Supersede classification comes from list.sh, not the model — same source /wrap-up uses for its at-save archive offer, so both skills agree on what supersedes what. Reasons: branch > slug > collision; ticket/cwd overlap is intentionally excluded.
• Liveness (branch-state + PR) is current-repo-only and opt-in via --check-branches — the queries run in pwd, so other repos always report unknown. PR state (from gh, auto-enabled when present) is ground truth and overrides the local branch-state heuristic; crucially it's the only signal that catches a squash-merge, where the feature branch is never an ancestor of the default tip. Liveness is deliberately separate from supersede: superseded = "a newer handoff continues this" (low-regret); merged-PR = "the work shipped" (low-regret); stale = "the branch is dead/abandoned and nothing supersedes it" (may be the only record — higher regret).
• Repo matching uses remote.origin.url first, then realpath of git-common-dir. Linked worktrees of one repo share the same key. Two independent clones with the same origin URL collapse to one row.
• .claude symlink unification has two flavours:
  • Non-bare — A's .claude symlinks to B's .claude subdir. A defers to B's identity. Display is B's basename.
  • Bare — A's .claude symlinks to B's repo root itself (B is just a scratch state-holder, not a working project). A keeps its own identity (and display); when B resolves on its own (e.g. via a handoff whose cwd lands inside B), a one-level sibling scan finds A's bare link pointing at B and defers up. Net effect: both ends group under A, the "real" repo. The follow is one-hop in either direction, so reciprocal links don't cycle.
• Pruned-worktree handoffs are pickable: the script walks up the recorded path to find the parent repo, so even after git worktree remove the handoff still groups correctly. When picked, the user resumes from their current checkout (or creates a fresh worktree).
• list.sh --bead <id> / --ticket <key> (consumed by /next and /start-ticket, not by this skill) emit an extra ---MATCHED-HANDOFFS--- section: current-repo, non-stale handoffs whose **Beads:** / **Jira:** header field contains that exact token. It reuses the same supersede + bead-closure + (with --check-branches) PR liveness machinery, so a bead/ticket resume surfaces only the live tip, never a superseded or shipped handoff — and because bead-closure is local, a handoff whose beads are all closed is filtered out even without --check-branches. Matching is exact-token and case-insensitive (bd-12 never matches bd-123). The flags leave every other section byte-identical, so this skill, /wrap-up, and /landscape are unaffected.