handoff
Skill0 starsChanged 9 days agoMITView on GitHub
Compress the current session into a handoff document so work can continue in a fresh session or move to a different agent. Use when the context window is filling up, when the user says to hand off, wrap up, continue later, or start fresh, or when switching to another tool or teammate mid-task.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- tanishq286/tq-forgetheir own version, first seen Nov 15, 2026
- niki914/zafirotheir own version, first seen Nov 15, 2026
- davidondrej/skillstheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- HiteSit/real-scientist-skillstheir own version, first seen Nov 15, 2026
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.
FabienDehopreSkilldecision-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
liufeng1976Skillsetup-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
AWSSkillto-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
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 87 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 51 projects that use this
LesaniSkillwriting-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
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- mattpocock/skills★ 325ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- GreyDGL/PentestGPT★ 16ksame name
- ykdojo/claude-code-tips★ 10ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 4.9ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
181 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.
In this repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/caveman-learn/CLAUDE.mdCLAUDE.md
- brainstormingSkill
- cavecrewSkill
- caveman-commitSkill
- caveman-compressSkill
- caveman-discoverSkill
- caveman-evidence-reviewSkill
- caveman-exploreSkill
- caveman-helpSkill
- caveman-learnSkill
- caveman-manageSkill
- caveman-optimizeSkill
- caveman-reviewSkill
- caveman-setupSkill
- cavemanSkill
- caveman-statsSkill
- diagnosing-superpowersSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- investigate-firstSkill
- karpathy-extendedSkill
- lean-buildSkill
- mcp-builderSkill
- megacaveSkill
- migrationSkill
- plugin-doctorSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- safe-refactorSkill
- scholastic-disputationSkill
- socratic-inquirySkill
- subagent-driven-developmentSkill
- surgical-patchSkill
- systematic-debuggingSkill
- terrasharkSkill
- test-driven-developmentSkill
- ultracaveSkill
- using-foundational-thinkingSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- verify-and-stopSkill
- writing-plansSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Write it to a file the next session can read — default docs/handoff-<topic>.md, or a path the user names.
- Distinctive: line 56
Verify before asserting: Every file path and command in the handoff must be real.
- Distinctive: line 58
State what is unverified: If tests were never run, say so.
- Distinctive: line 60
Keep it short enough to be read: If it exceeds roughly two pages, the detail belongs in the codebase or a design doc that the handoff links …
“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.
Files
Handoff
Produce a document that lets someone — a fresh session, a different agent, or a person — resume this work without re-deriving what was already established.
When to reach for this
- Context is filling and the session will be summarized or restarted
- The user is stopping for the day and wants to resume cleanly
- Work is moving to another agent (Codex, Gemini) or another person
- A long investigation reached a conclusion worth preserving beyond this session
What makes a handoff good
A handoff is not a transcript summary. It is the minimum a competent stranger needs to continue. Optimise for what would otherwise be re-derived at cost: decisions and their reasons, dead ends already ruled out, and the exact next action.
Write it to a file the next session can read — default docs/handoff-<topic>.md, or a path the user names. Do not print a long handoff into the conversation; the point is that it survives the conversation ending.
Structure
# Handoff: <topic>
**Status:** <one sentence: what is done, what is in flight>
**Updated:** <absolute datetime>
## Goal
What we are trying to achieve, and why. Absolute dates, no "yesterday".
## Current state
What exists now. Name real files and functions with paths. Distinguish
"built and verified" from "built but untested" from "planned".
## Decisions made
| Decision | Why | Alternatives rejected |
Enough that the next session does not reopen a settled question.
## Dead ends
What was tried and did not work, and the symptom. This is often the highest
value section: it is pure cost to rediscover.
## Next action
The single specific thing to do next, concrete enough to start immediately.
Then anything queued behind it.
## Open questions
Things genuinely undecided, and who or what can decide them.Rules
- Verify before asserting. Every file path and command in the handoff must be real. A handoff that points at a function that does not exist is worse than none — the reader trusts it and loses time.
- Absolute dates. "Last Tuesday" is meaningless to a session that starts in three weeks.
- State what is unverified. If tests were never run, say so. Never imply completion that did not happen.
- Prefer pointers to prose. A path plus a line number beats a paragraph of description.
- Keep it short enough to be read. If it exceeds roughly two pages, the detail belongs in the codebase or a design doc that the handoff links to.
Cross-agent handoffs
When the next reader is a different tool, avoid Claude-specific vocabulary. Say "run the tests with npm test" rather than naming a slash command that only exists here. Skill and plugin names are Claude-specific; describe the capability instead. AGENTS.md is the portable convention most agents read, so a handoff that will cross tools belongs alongside it rather than in Claude-only configuration.
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.

