agentleFS
Sign inStart free
HeathWangHeathWang/hw-cc-plugin/skills/handoff/SKILL.md

handoff

Skill1 starsChanged 3 months agoMITView on GitHub

Use when the user asks to create a handoff, session summary, context compact, continuation note, 交接文档, 压缩上下文, or instructions for the next agent to resume work later.

191 other projects use a version of this, 80 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

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 7

    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 summarizing the current conversation so a fresh agent can continue the work.

    line 11
  2. Very specific:

    Use a clear filename like handoff-YYYYMMDD-HHMM.md, then report the saved path to the user.

    line 26
  3. Distinctive:

    Do not duplicate content already captured in other artifacts such as PRDs, plans, ADRs, issues, commits, or diffs.

    line 41
  4. Distinctive:

    If the user passed arguments, treat them as the next-session focus and tailor the document accordingly.

    line 45
  5. Distinctive:

    After successfully saving the handoff, reply with exactly:

    line 49
  6. Distinctive:

    Do not save the handoff inside the current repository.

    line 64
  7. Distinctive:

    Do not include secrets or raw private data.

    line 65
  8. Distinctive:

    Do not omit the final saved path.

    line 66

“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

Overview

Write a handoff document summarizing the current conversation so a fresh agent can continue the work. Save it to the user's OS temporary directory, not the current workspace.

When to Use

  • User asks for a handoff, session summary, context compact, continuation note, or next-agent instructions
  • User says "生成交接文档", "交接文档", "压缩上下文", "给下个 agent", "下一轮继续", or "接着做"
  • User passes arguments describing what the next session should focus on

Output Location

Save the document outside the workspace using the OS temp directory:

  • macOS/Linux: use $TMPDIR when set, otherwise /tmp
  • Windows: use %TEMP%

Use a clear filename like handoff-YYYYMMDD-HHMM.md, then report the saved path to the user.

Required Sections

  • Objective and requested next-session focus
  • Current status and completed work
  • Pending work and next recommended steps
  • Files touched or artifacts to inspect
  • Commands, tests, or checks already run
  • Known failures, risks, and constraints
  • User preferences and project rules that matter
  • Suggested skills with reasons

Constraints

Do not duplicate content already captured in other artifacts such as PRDs, plans, ADRs, issues, commits, or diffs. Reference them by path or URL and summarize only the current status needed to continue.

Redact sensitive information, including API keys, passwords, tokens, credentials, private keys, secrets, and personally identifiable information.

If the user passed arguments, treat them as the next-session focus and tailor the document accordingly.

Final Response

After successfully saving the handoff, reply with exactly:

  1. One brief confirmation in the user's language.
  2. A fenced text code block containing only the absolute saved path.

Example:

/tmp/handoff-20260715-1713.md

The code block is the copyable file information. Keep labels, bullets, and other metadata outside it.

Common Mistakes

  • Do not save the handoff inside the current repository.
  • Do not include secrets or raw private data.
  • Do not omit the final saved path.

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