agentleFS
Sign inStart free
EnjoyoerEnjoyoer/loadout/skills/orchestration/handoff/SKILL.md

handoff

Skill0 starsChanged 26 days agoMITView on GitHub

Hand off current work by committing a comprehensive update of the root STATUS.html and LESSONS.md, creating the pair if missing. Use when the user asks for a handoff, resume note, continuation doc, or context packet, or before a PM or workstream owner migrates or is replaced. Works with or without $repo-lessons. Writes no separate handoff file.

191 other projects use a version of this.

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

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $repo-lessons is installed, follow its root, ownership, STATUS.html, and LESSONS.md rules.

    line 10
  2. Very specific:

    Create if missing: If STATUS.html or LESSONS.md is absent at that root, create it there.

    line 13
  3. Very specific:

    Commit: If the root is in a Git repository, commit only STATUS.html and LESSONS.md with a message such as Handoff: <short topic>.

    line 15

“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

A handoff is a full, detailed update of the root STATUS.html and LESSONS.md, committed. There is no handoff file, and the successor has nothing to consume: it resumes by reading the pair.

If $repo-lessons is installed, follow its root, ownership, STATUS.html, and LESSONS.md rules. Otherwise use the fallback below.

  1. Resolve the root. Use the owned root: the current project root you were working in, or its Git root if inside a repository. A Worker never writes into a PM's pair; if the only pair in reach belongs to someone else, stop and report that.
  2. Create if missing. If STATUS.html or LESSONS.md is absent at that root, create it there. An explicit handoff request authorizes this, even in a project that had no memory pair; it is the one exception to the $repo-lessons rule against seeding unrelated projects.
  3. Update the pair. Rewrite all five STATUS.html sections, preserving every active identifier and owner gate, so a successor can continue from this file alone. Add every durable, non-obvious fact from the session to LESSONS.md within its cap. Point to source paths, commits, and PRs instead of copying them. If the user passed arguments, treat them as the next session's focus.
  4. Commit. If the root is in a Git repository, commit only STATUS.html and LESSONS.md with a message such as Handoff: <short topic>. Leave unrelated changes unstaged. Push or open a PR only when that repository's own instructions require it for memory changes.
  5. Report the commit hash (or that the root is not a Git repository) and one line saying the pair is ready for the successor.

Fallback format (without $repo-lessons)

  • Edit both files in place. Never write backups, dated copies, or archives.
  • STATUS.html: browser-openable current-state dashboard with, under the project name, exactly these sections in order: Waiting on you (owner decisions, with recommendation), In flight (each item with its exact agent, branch, PR, and session IDs, state, and next action), Blocked (dependency and who it waits on), Done last 7 days, Health line (last evidenced check, known gaps, as-of time). No raw logs, secrets, or history.
  • LESSONS.md: at most 8,192 UTF-8 bytes, newest first, only facts whose loss would likely cause a future mistake. Each entry:
### YYYY-MM-DD - short title
- **Status:** active | superseded | needs-review
- **Verified:** YYYY-MM-DD | not verified
- **Evidence:** project-relative path, source URL, or commit ID
- **Review when:** concrete event that can invalidate this fact
- **What:** ...
- **Why it matters:** ...
- **Fix / workaround:** ...

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