handover
Skill3 starsChanged 27 days agoMITView on GitHub
Write a handover for the next agent in the project's memory, so it knows what to do, why, how and where the owner's word is still needed; then have a cheap model check every claim in it. Use when the owner asks for a handover, or when a session nears the end of its context with work open.
53 other projects use a version of this.
Adopted by
Most recently taken up by
- Kealman/cland-v0their own version, first seen Nov 15, 2026
- gjoranv/claude-plan-skillstheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- thiagobluhm/o1memtheir own version, first seen Nov 8, 2026
- randommonicle/claude-skillstheir own version, first seen Nov 5, 2026
- hmislk/hmistheir own version, first seen Nov 2, 2026
Used with
Projects with it also use harness-init, incident 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.
steptianSkillharness-init
初始化 .harness 开发框架,集成代码修改影响范围评估和测试覆盖建议功能。触发词:'初始化新项目'、'harness init'、'更新 harness'、'分析影响范围'、'评估修改影响'
Also in 3 projects that use this
JkudjoSkillincident
Production incident response — structured triage, hypothesis tree, safe remediation, incident record
Also in 3 projects that use this
nicolasestremSkillbrainstorm
Structured idea generation and solution exploration with systematic analysis.
Also in 4 projects that use this
GoogleSkillto-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Also in 4 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 4 projects that use this
GoogleSkillgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Also in 4 projects that use this
- +2 more from google
Other versions53 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 53
- me2resh/apexyard★ 542same name
- hmislk/hmis★ 245same name
- chenklein26-maker/Harness-Starter★ 119same name
- k1ein-chen/Harness-Starter★ 119same name
- eai-org/agent-toolkit★ 94same name
- manusco/resonance★ 38same name
- chacosoldier/compabob★ 34same name
- randommonicle/claude-skills★ 27same name
- yagizdo/quiver★ 16same name
- L-X-T/ng-agentic-skills★ 13same name
43 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
2
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
- Very specific: line 23
Update the file's frontmatter description (it is what loads in every session) and the handover's line in MEMORY.md, both naming the new …
- Distinctive: line 32
Every fact in the block is read off a command run now, never recalled:
- Distinctive: line 97
Start a subagent on the cheapest model (Haiku), read-only, with this brief, filling in the paths:
“Common” is measured: kept by at least 6 in 10 of the 40 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.
Files
Handover
A handover is what the next agent cannot learn from the code, git, the rule files or the memory index: the owner's intent, the reasons behind what was built, what was turned down, the state of the world, the traps met, and where the owner's word is still needed. Everything else it only points at.
It is written for an agent that will be responsible for what it does next. So it is a set of claims to check, not proof, and it says so to its reader.
Where it goes
- In memory, never in the repository: the project's memory directory under
~/.claude/projects/, fileproject_handover.md. - A new block at the top, headed
## 0-<NAME>, session <id> (<date>, <UTC window>). READ THIS FIRST; every block below is history. Mark the block that was first until now as history. - Update the file's frontmatter
description(it is what loads in every session) and the handover's line inMEMORY.md, both naming the new block and HEAD. - A correction from the owner that must hold from now on goes to a feedback memory of its own, not to the handover: the handover goes stale when its work is done, a rule must not.
1. Gather the facts, by commands only
Every fact in the block is read off a command run now, never recalled:
- branch, HEAD, and what is pushed: compare with every remote branch it
could be on (
git log --oneline -1 origin/<branch>,git rev-list --count origin/<branch>..HEAD); - what is uncommitted, and whose it is (
git status --short,git diff <file>): lines the owner keeps uncommitted are named as theirs; - the last runs of each suite, with the counts read from their output, and the commit they ran at; what no run has checked is said as such;
- what is still running: servers, worktrees, background agents.
2. The owner's words, verbatim
Find the session's transcript (~/.claude/projects/<project>/<session>.jsonl)
and take every message the owner wrote this session: the entries of type
user, and queue-operation for what they sent while a turn ran. Search it
with grep or a short script that reads it line by line; never print it
whole. Quote each message word for word, with its UTC time, and after it one
line of what was answered or done. Mark plainly what the owner approved and
what they have not said yes to yet.
Words of an earlier session that the work rests on are quoted the same way, with that session's id and where they stand in its transcript.
3. Write the block
In this order, each part short; a part with nothing to say is left out.
- Before your first answer. The transcript's path, and: read the quoted words there before answering "what next"; never answer it from this block alone.
- You are responsible for what you do next. This block is a set of
claims. Before your first step, check what you will build on, cheaply:
git statusandgit log; that a file, a name or a test it names exists; the owner's words in the transcript. Where the block and git or the code differ, git and the code win: say so. A reading of the owner's words this block calls unconfirmed is a question, not a decision. Do not run whole suites to check the block: the counts below stand until you change their code. Run the tests of the part you touch, as the project's rule on test runs says. - State, checked at
<UTC time>. The facts of step 1. - The owner's words. Step 2.
- Done. Each piece by commit, and for each: what it did; why — the owner's motive in their words; why this construction; what was turned down and why, so nobody improves it back; how it was checked (a test seen failing, a reviewer, a run with its count), or that nothing checked it.
- Readings the owner has not confirmed, each with what it rests on.
- What the owner will see changed.
- Next. What waits for the owner's word, and what does not. For each
step, the approved line it carries out, and the sources to read for it —
memory files by
[[name]], TODO sections, files. Never a plan retold with a construction the owner did not approve. - Other open work: everything left or deferred, written also where its doer reads it (the project's TODO), with why it is left and whose decision it waits on.
- Traps met: what cost time and is in no file — a tool that lies, a command that needs a flag, a gate that sees more than it seems to.
- How the work was done, where it should go on that way: the cycle of a piece, its reviews, how commits are made.
Point at rules, never retell them. Write it as an index: the next agent reads the block, then only what its next step names.
4. Have it checked
Start a subagent on the cheapest model (Haiku), read-only, with this brief, filling in the paths:
You check a handover note against the facts. You change nothing: read only. Spawn no subagents. Run no test suite and no build: where the note gives a test count, say "not checked by a run" unless something you can read contradicts it.
The note: the block
<heading>at the top of<memory>/project_handover.md, its frontmatterdescription, and its line in<memory>/MEMORY.md. The repository:<repo>. The transcript it quotes:<transcript>— large; search it with grep or a short script, print only short excerpts.Check every factual claim by a command: branch, HEAD, what is pushed and what is not; uncommitted files; each commit named exists and does what the note says; each file, name, setting and test it names exists; each quote of the owner stands word for word in an entry of type
userorqueue-operationat the time given, to the minute; each[[name]]is a memory file whose frontmatternamematches; each item called open is still open where the note says it is.Then read the block as an agent that knows nothing else would, and say what it lacks to know what to do first, why, where the owner's word is still needed, and how it would check its own work; and where it can be read two ways.
Report, at most 40 lines: each claim, OK or WRONG with what you found; then what is missing or unclear. Facts only.
Why a separate model: the writer believes its own block. Why the cheapest: the check is reading and searching, not judgement, and it must not cost the owner a heavy model's quota.
5. Fix, then report
Correct every WRONG, close every gap the check found that a next agent would need, and fix the repository where the check finds it disagrees with itself (a CHANGELOG line the code contradicts). Then tell the owner, in a few lines: where the block is, what the check found and what you changed.
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
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.

