agentleFS
Avijit07xAvijit07x/claude-db/skills/handoff/SKILL.md

handoff

Skill233 starsChanged 3 months agoApache-2.0View on GitHub

Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why. Saves it to project memory so the next chat sees it at the start, and prints it so it can be pasted into a message or a pull request. Use when the user ends a piece of work, switches tasks, or hands the project to someone.

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

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

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 3

    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. Distinctive:

    Run this from the project root to see what memory and git already know:

    line 10
  2. Very specific:

    Use only what this chat or the output showed.

    line 45
  3. Very specific:

    If there is no clear next step, write - Next: no clear next step yet.

    line 46
  4. Distinctive:

    Leave out secrets, tokens, passwords and personal data.

    line 47
  5. Very specific:

    Call the remember memory tool once, with these exact values:

    line 55
  6. Distinctive:

    If the memory tool is not available, still print the note and say it was not saved.

    line 71

“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

Write a handoff note

1. Gather the facts

Run this from the project root to see what memory and git already know:

claude-db catchup

Combine that with what happened in this chat. The chat is the best source for what was done and what is still open. The output fills gaps and checks dates. If it shows a Last handoff, that is the note you will carry forward in step 2.

2. Write the note

The first line is the title and has today's date. Get it with date '+%b %-d'. Then write at most 8 lines, each under about 200 characters. The next chat reads this note at its start, so every line costs context.

Handoff, Oct 7:
- Done: timers, queue, mail family.
- Open: PR #18 not merged.
- Next: ask which retries to change on the worker queue.
- Decided: retries stay at 3, because the queue already backs off.
- Rejected: a second worker pool, because it doubled the mail cost.
- Watch out: tests read dist/, so run the build first.
- State: branch v0.12, 4 files uncommitted, last commit 1db3638.

Lines:

  • Done, Open and Next are always there. One line each.
  • Decided, Rejected, Watch out and State only when there is something real to say. Never pad.
  • Rejected and Decided give the reason after "because". A rejected idea with no reason is not worth a line.
  • State comes from the catchup output, not from memory: the Branch line and the newest of the Recent commits. Add a pull request number only if this chat mentioned one.
  • Decided and Rejected start from Decisions and dead ends in the output, plus this chat.
  • Name real things: a file, a pull request number, a command, a decision. Do not write various changes.
  • Use only what this chat or the output showed. Mark anything you are unsure of with (guess).
  • If there is no clear next step, write - Next: no clear next step yet. Do not invent one.
  • Leave out secrets, tokens, passwords and personal data.

Carry forward. Keep a line from the previous handoff when it is still true and still matters, and add the date to it, for example (Oct 5). Drop what is finished or wrong. If the note is over 8 lines, shorten lines or drop the oldest finished ones. Never drop a Rejected line that is still true.

3. Save it

Call the remember memory tool once, with these exact values:

  • text: the note
  • key: handoff
  • kind: context
  • tags: ["handoff"]

The key makes a new handoff replace the old one for this project, so there is one current note. The next chat sees it at the start under Last handoff. It is shown for 14 days. Only the first 8 lines are shown, each cut at about 220 characters.

4. Print it

Show the note in a code block so the user can paste it into a message or a pull request. Then say in one line that it was saved, and that it replaces any earlier handoff for this project.

If the memory tool is not available, still print the note and say it was not saved.

Sharing

A teammate sees the saved note when both of you use the same Postgres or MongoDB database. With the default SQLite file on one machine, the printed note is the way to share it.

Shipped with claude-db. It is replaced when claude-db updates.

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.