agentleFS
TomSzenessyTomSzenessy/AI_TEMPLATE/.agents/skills/agent-handover/SKILL.md

agent-handover

Skill0 starsChanged 10 days agoMITView on GitHub

Start, resume, or conclude substantial cross-session work while preserving a concise, redacted handover and a concrete next action.

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

6 rules. About 0 are common, 4 are distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when work may cross a session, branch, machine, model, or owner.

    line 8
  2. Very specific:

    Check directly for root HANDOVER.md.

    line 13
  3. Distinctive:

    Treat the working tree and current repository state as authoritative when they disagree.

    line 17
  4. Distinctive:

    Keep the handover limited to state another actor cannot reconstruct from Git: current goal, decisions, validation, blockers, and the next …

    line 23
  5. Very specific:

    Run make handover to create root HANDOVER.md from ../../../docs/handoffs/TEMPLATE.md with the git facts pre-filled (it never overwrites an …

    line 29
  6. Distinctive:

    Update every section concisely and remove stale claims.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Agent handover

Use this skill when work may cross a session, branch, machine, model, or owner. For a short self-contained change, use the normal issue and verification loop.

Start or resume

  1. Check directly for root HANDOVER.md; read it completely if present. A hooked host already printed it in the session brief (make start otherwise), and .agent/checkpoint.md holds the last pre-compaction snapshot.
  2. Compare it with the current branch, working tree, manifest, and linked issue. Treat the working tree and current repository state as authoritative when they disagree.
  3. Preserve unrelated uncommitted changes and secrets boundaries.

While working

Keep the handover limited to state another actor cannot reconstruct from Git: current goal, decisions, validation, blockers, and the next concrete action. Reference issues, commits, specs, and ADRs instead of copying them.

Conclude or pause

  1. Run make handover to create root HANDOVER.md from ../../../docs/handoffs/TEMPLATE.md with the git facts pre-filled (it never overwrites an existing one).
  2. Update every section concisely and remove stale claims.
  3. Use ../../../docs/handoffs/TEMPLATE.md for a committed cross-machine handoff, then add it to the docs index.
  4. State in the final response whether the handover was updated and what remains.

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.