From handoff
Snapshot the in-progress task and still-open decisions before a `/clear` or new session, so the next session resumes where this one left off. A lightweight, local task frame — not a conversation summary. Use when the user asks to "save handoff", "save context", "prepare handoff", "write handoff", "before /clear", "before I clear", "clear handoff", "discard handoff", "clean handoff", "finalize", "wrap up", "I'm done", "/handoff", "handoff", "conversation too long", "let's pick this up in a new chat", "end", or "goodbye", or otherwise signals an imminent `/clear` or end of task.
How this skill is triggered — by the user, by Claude, or both
Slash command
/handoff:handoffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Preserve the irreducible residual across `/clear`: what was in
Preserve the irreducible residual across /clear: what was in
progress and what's still undecided. Hooks handle wipe-before-write
and extract-after-write — your job is the task file.
If durable learnings surfaced this session, capture them in auto-memory now. Skip if nothing durable surfaced — do not force.
First, decide both of the following without making any tool calls:
Then, in the same turn, issue the writes and run the memory probe:
./.claude/autorename — sole line is the session title (always)./.claude/handoff-task.md — only if there's an active taskhandoff-memory-probe (Bash) — deterministic gitlore-memory checkIf there's no active task, omit handoff-task.md — the activation hook
already finalized the session.
handoff-memory-probe prints nothing when there is no gitlore-managed
memory to commit — finish normally. If it prints a directive, the
directive itself states what to do; follow it exactly. The usual case
asks you to summarize the pending memory changes in 1-3 sentences, get
the user's approval (they may edit the summary), then run the commit
command it names — never commit without that approval. The probe owns
the decision — do not re-derive it or inspect the submodule yourself.
Task file template:
## Current task
<ONE SENTENCE describing what was in progress. Not a recap. What needs
to resume when a fresh agent picks up. Overflow belongs in memory or
git.>
## Open decisions
- <Unmade choice, phrased as a decision still to make, with enough
context to decide.>
<Drop the section if there are no open decisions. No filler.>
Task file rules:
# heading — the read-time hook prepends one when it assembles
the frame next session../.claude/handoff-task.md — the hook reads
this exact path.## Open decisions. Those go to feedback memory.handoff-task.md. The template is fixed.references/design.md — design rationale: what the residual is
and why the agent-authored task file plus mechanical extract split.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub ddaanet/claude-plugins --plugin handoff