agentleFS
borkwebborkweb/skills/skills/core/handoff/SKILL.md

handoff

Skill8 starsChanged 5 months agoMITView on GitHub

Write a handoff document so another agent or a fresh session can continue this work. Use for "handoff", "hand this off", "write a handoff", "continue this in a new session" or "pass this to another agent". For deciding whether to compact or clear, use session-budget.

191 other projects use a version of this, 87 of them edited.

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

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a handoff document summarising the current conversation so a fresh agent can continue the work.

    line 7
  2. Distinctive:

    If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

    line 9
  3. Distinctive:

    When continuing a complete run, include its ledger and per-slice result paths under Pointers, and preserve authorization, frozen gates, …

    line 12
  4. Distinctive:

    Don't duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs).

    line 32
  5. Very specific:

    If a section has no real content, write None.

    line 33
  6. Distinctive:

    Keep it tight. A handoff is a launchpad, not a transcript.

    line 34

“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

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Create a unique temporary directory with the platform's secure temp helper (for Node, fs.mkdtempSync(path.join(os.tmpdir(), "handoff-"))) and write handoff.md inside it. Report the absolute path.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

Preserve the actual receiving runtime and resolved role/model configuration under Key context. Do not inject orchestration defaults into an unrelated continuation. Writing a handoff does not launch a worker or change the active model. When continuing a complete run, include its ledger and per-slice result paths under Pointers, and preserve authorization, frozen gates, unresolved rulings, and agent IDs needed to resume. The receiving Codex must verify agent liveness; an ID from a previous session is not proof that a worker is still running.

Document structure

The handoff is read by another agent, so its shape is fixed. Produce exactly these eight sections, in this order, with these headings verbatim. Lead with intent and next steps, not narrative history — a fresh agent should scan top to bottom and start working.

  1. # Handoff: <short title> — one line naming the work.
  2. ## Goal — what the next session is trying to accomplish, in 1–2 sentences. If args were passed, this reflects them.
  3. ## Current state — what's done and working right now. Bullets, past tense.
  4. ## Next steps — the concrete actions to take next, ordered, each an imperative ("Wire up X", "Run Y"). The most important section: make it actionable from a cold start.
  5. ## Open questions / blockers — unresolved decisions, things waiting on someone, known risks.
  6. ## Key context — the non-obvious things: decisions made and why, gotchas, dead ends already ruled out. Skip anything a fresh agent could read straight from the code or the linked artifacts.
  7. ## Pointers — paths and URLs to the artifacts that hold the detail: PRDs, plans, ADRs, issues, branches, key files (path:line). Reference them; don't copy their contents in.
  8. ## Suggested skills — which skills the next session should use, if any, and for what.

Rules

  • Don't duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead — that's what Pointers is for.
  • If a section has no real content, write None. under it rather than padding with filler or inventing items to fill space. An empty Open questions is fine; a fabricated one is not.
  • Keep it tight. A handoff is a launchpad, not a transcript.

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.