agentleFS
pfeffpfeff/claude-skills/skills/handoff/SKILL.md

handoff

Skill3 starsChanged 3 months agoMITView on GitHub

Write and rehydrate a durable session-handoff document so a fresh, zero-context session resumes work without inheriting bloated history. Use when approaching the context limit, before /clear, at end of session, or when handing work to another session or agent. Two operations — write (capture current state to a handoff doc) and rehydrate (re-ground a fresh session from it, reconciling against live state). Host-agnostic; discovers the handoff file per project. Invoke via /handoff (write) or /handoff rehydrate.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-mapping, setup-ts-deep-modules and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 8 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 93 projects that use this

  • GoogleSkill

    ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 87 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 51 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 54 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only the operation that applies to the current invocation.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 172 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/handoff — session-handoff document

Writes a durable, inspectable Markdown state file to disk so a fresh, zero-context session can pick up exactly where the last one left off — instead of inheriting a bloated conversation or hoping lossy compaction kept the right things. The handoff doc is the explicit, reviewable alternative to /compact: you read it, verify it, then /clear.

This is the interactive-operator-layer primitive. It is human-readable and operator-facing — distinct from machine durability mechanisms (e.g. an AC serialized image). Use it for sessions that stay interactive across a /clear, a compaction, an end-of-day stop, or a handoff to another operator/agent.

Surface

/handoff [focus hint]        # write/refresh the handoff doc
/handoff rehydrate           # re-ground a fresh session from the doc
  • A trailing focus hint (e.g. /handoff focus on the auth refactor) biases what write emphasizes; it does not change the schema.
  • The handoff file location is discovered, not configured per-call — see references/protocol.md.

Operations (load on demand)

OperationWhenFile
Write the handoff doc/handoff (no rehydrate)operations/write.md
Rehydrate a fresh session/handoff rehydrateoperations/rehydrate.md

Read only the operation that applies to the current invocation.

Doctrine source-of-truth

  • The document schema is read from references/schema.md. It is the durable contract — never inline it into an operation, and never silently drop a section.
  • The discovery rule, hand-off timing, and staleness-reconciliation procedure live in references/protocol.md.

Both files are read at operation time. If either is missing, fail loud rather than improvising a schema — recover from git history.

Hard rules

  1. Always Write to disk — never just display the doc. A handoff that only appears in chat dies with the context it was meant to outlive.
  2. Review before reset. write reports the path and reminds the operator to read it before /clear; it does not itself clear or compact.
  3. Reconcile, don't assert. rehydrate cross-checks the doc against live state (git, and GOAL.md/coord if present) and flags divergence rather than trusting a possibly-stale doc.
  4. No auto-act on rehydrate. Emit a re-grounding summary and hand control back to the operator/role.

See also

  • references/schema.md — the handoff document schema (frontmatter + sections)
  • references/protocol.md — discovery rule, when to hand off, staleness reconciliation
  • task-workflow /finish, chief-of-staff End-of-Session Capture — knowledge capture (Obsidian session-journal, metrics). Complementary, not the same surface: those are durable knowledge; a handoff is ephemeral session state.
  • goal-tree /resume-project — tree-status rehydration from CLAUDE.md + GOAL.md + coord. /handoff rehydrate layers a narrative re-grounding on top.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.