agentleFS
Sign inStart free
pushprove-maxpushprove-max/Commandeck/skills/handoff/SKILL.md

handoff

Skill3 starsChanged 6 days agoApache-2.0View on GitHub

Checkpoint main and restart it in a fresh pane now, below the 200K clear line. Use when the owner runs /handoff or says "hand off", "checkpoint and restart", "fresh main". Main session only.

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

3 rules. 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write ~/.claude/checkpoints/<session id>.md in ONE Write from the fixed template ${CLAUDE_PLUGIN_ROOT}/templates/checkpoint.md: every field …

    line 24
  2. Distinctive:

    Stop hook is the one supported way.

    line 36
  3. Very specific:

    If this pane is still here at the owner's next prompt, the restart did not finish: a HANDOFF NOT DONE line names why.

    line 39

“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

Runs the same checkpoint-and-restart main does at the 200K line (${CLAUDE_PLUGIN_ROOT}/templates/main-session.md, "Main never compacts"), on demand. Main session only: in a linked worktree context-clear-stop.sh ignores it.

Session id: ${CLAUDE_SESSION_ID}. If that is not substituted, it is the newest *.jsonl file name under ~/.claude/projects/<this project>/.

Board when this skill loaded (fill the checkpoint from it; do not re-run it):

bash "${CLAUDE_PLUGIN_ROOT}/scripts/board.sh" 2>&1 || true
  1. Finish the step in hand. Start nothing new.
  2. Write ~/.claude/checkpoints/<session id>.md in ONE Write from the fixed template ${CLAUDE_PLUGIN_ROOT}/templates/checkpoint.md: every field filled or "none", live units with pane handles and task ids, what each waits on and the exact next command, rulings not yet in memory, the queue, gotchas, what was ruled out, how to verify, and what closed since the last checkpoint. Older open items are carried by a Carries open items of: <file> line, never copied. Under 5KB.
  3. touch ~/.claude/checkpoints/<session id>.handoff
  4. Tell the owner, in one line: "Handing off: a new main pane opens when this turn ends, says 'Handoff done' first, and this pane closes once it has taken over." Then end the turn. Do not type /clear, and never open a main pane yourself: the plugin's guard refuses a hand-made one, and the Stop hook is the one supported way. It opens the fresh main pane, types the resume prompt there, and closes this pane only after the new one has taken it; a step that fails leaves this pane up as main.
  5. If this pane is still here at the owner's next prompt, the restart did not finish: a HANDOFF NOT DONE line names why. Read it to the owner, fix what it names (most often the checkpoint), and end the turn to try again.

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