agentleFS
Sign inStart free
kjendrzycakjendrzyca/public-skills/skills/handoff/SKILL.md

handoff

Skill1 starsChanged 3 months agoMITView on GitHub

Compact the current conversation into a handoff document for another agent to continue from. Use when the user asks for a handoff, session transfer, continuation note, context summary for a fresh agent, or a document describing what the next session should pick up.

191 other projects use a version of this, 71 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 compact handoff document so a fresh agent can continue the work without replaying the full conversation.

    line 9
  2. Distinctive:

    Write the document to the user's OS temporary directory, not the current workspace.

    line 14
  3. Very specific:

    Use a clear filename such as handoff-YYYYMMDD-HHMMSS.md.

    line 17
  4. Distinctive:

    Keep the handoff self-contained enough for continuation, but do not duplicate material already captured in artifacts such as PRDs, plans, …

    line 18
  5. Distinctive:

    Do not start the continuation work.

    line 20
  6. Distinctive:

    Prefer concrete paths, command names, and status facts over narrative detail.

    line 35

“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 compact handoff document so a fresh agent can continue the work without replaying the full conversation.

Workflow

  1. Identify the next-session focus from the user's request. If the user included a focus phrase or arguments, treat that as the intended focus and tailor the handoff to it.
  2. Write the document to the user's OS temporary directory, not the current workspace.
    • On macOS/Linux, use $TMPDIR when set, otherwise /tmp.
    • On Windows, use %TEMP%.
    • Use a clear filename such as handoff-YYYYMMDD-HHMMSS.md.
  3. Keep the handoff self-contained enough for continuation, but do not duplicate material already captured in artifacts such as PRDs, plans, ADRs, issues, commits, diffs, or reports. Reference those artifacts by path or URL instead.
  4. Redact sensitive information, including API keys, passwords, tokens, private auth material, personal identifiers, and any content the user clearly did not intend to hand to another agent.
  5. Do not start the continuation work. Produce the handoff file and report its path.

Document Shape

Include these sections when relevant:

  • Purpose: what the next agent should focus on.
  • Current State: where the work stands now.
  • Completed Work: concise bullets for what was already done.
  • Key Artifacts: paths, URLs, PRs, issues, commits, plans, reports, or diffs to inspect instead of duplicated content.
  • Decisions And Constraints: important choices, assumptions, style rules, safety constraints, and open questions.
  • Suggested Skills: skill names the next agent should invoke, with one short reason each.
  • Next Steps: ordered continuation steps.
  • Verification: checks already run, checks still needed, and known blockers.

Prefer concrete paths, command names, and status facts over narrative detail. If a fact is uncertain, mark it as uncertain instead of filling the gap.

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