agentleFS
Sign inStart free
ehnruizehnruiz/claude-skills/skills/handoff/SKILL.md

handoff

Skill3 starsChanged 29 days agoMITView on GitHub

Write a handoff note so a fresh session can continue this one's work. Use when the user says to hand off, wrap up, or save progress for later, or when a long session is about to end with work still open.

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

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 4

    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:

    Write a note that lets a session with no memory of this one carry on without asking what happened.

    line 10
  2. Distinctive:

    Put Goal and State first; tools that preview a handoff often show only its opening.

    line 27
  3. Distinctive:

    Leave out secrets: API keys, tokens, webhook URLs, passwords, personal data.

    line 32
  4. Distinctive:

    If the user passed an argument, shape the note around that focus.

    line 33

“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

Write a note that lets a session with no memory of this one carry on without asking what happened.

Project copy first. If the repository has its own .claude/skills/handoff/SKILL.md, read it and follow it instead of this file. A skill installed for all your projects outranks a project skill with the same name, so without this step a repository's own version of this skill would never run.

Where

Save it to ~/.claude/projects/<project slug>/handoffs/<YYYY-MM-DD>-<topic>.md, the topic in two to four kebab-case words. The slug is Claude Code's own folder name for the main checkout's path (every character that is not a letter or digit becomes -), so a session in a git worktree saves beside the others; python3 hooks/handoff_notice.py --print-dir from this repository's install prints it. Keep it outside the repository so it never lands in a commit, and outside any session scratch directory, which the next session cannot see. Tell the user the path.

What goes in it, in this order

  1. Goal: one or two sentences on what the work is for.
  2. State: what is done, and how each "done" was verified (the command and its result, the PR, the commit).
  3. Decisions: what was decided and why, so the next session does not reopen it.
  4. Open questions: what is still undecided, and who decides it.
  5. Next steps: in order, each one concrete enough to start on.
  6. Useful skills and agents: which ones fit the next steps.

Put Goal and State first; tools that preview a handoff often show only its opening.

Rules

  • Point to issues, PRs, commits and files by number, hash or path. Do not copy their content in.
  • Leave out secrets: API keys, tokens, webhook URLs, passwords, personal data.
  • If the user passed an argument, shape the note around that focus.

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.

Check your setup, free