agentleFS
Sign inStart free
gleicongleicon/devskills/skills/ds-handoff/SKILL.md

ds-handoff

Skill20 starsChanged 46 days agoMITView on GitHub

Compact the current conversation into a handoff document so a fresh agent can continue the work.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    When invoked, write a handoff document summarizing the current conversation, then hand the path back.

    line 7
  2. Very specific:

    Create a temp directory with mktemp -d.

    line 11
  3. Distinctive:

    Write the handoff document to that path: current goal, what is done, what remains, key decisions, and open questions.

    line 12
  4. Distinctive:

    Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs).

    line 18
  5. Distinctive:

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

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

When invoked, write a handoff document summarizing the current conversation, then hand the path back.

Process

  1. Create a temp directory with mktemp -d; the output path is <that-directory>/ds-handoff.md.
  2. Write the handoff document to that path: current goal, what is done, what remains, key decisions, and open questions.
  3. Suggest which commands the next session should use, if any.

Rules

  • Redact secrets and PII before writing. The handoff is a plaintext file pasted into a fresh session — strip API keys, tokens, passwords, and personal data from anything carried over; point to where a secret lives, never its value.
  • Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
  • If the user passed arguments, treat them as a description of what the next session will focus on and tailor the document accordingly.

Output

Display the handoff document path after writing.

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