handoff
Skill1 starsChanged 3 months agoMITView on GitHub
Write a handoff document so a fresh session (or a different account) can continue this work without starting from scratch. Saves to handoff/ in the project root. Also invoked automatically when session usage crosses the configured threshold.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- xiaoxiaosrm/dsh-mattpocock-skillstheir own version, first seen Nov 8, 2026
- ethosagent/ethostheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- glebis/claude-skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 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★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- GreyDGL/PentestGPT★ 16ksame name
- ykdojo/claude-code-tips★ 10ksame name
- ArcReel/ArcReel★ 6.3ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame 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 repository4 other files it gives its agents.
- bigstep-brandingSkill
- open-prSkill
- start-ticketSkill
- tech-docSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 172 edited versions we read keep these.
5
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
- Distinctive: line 9
Write a handoff document that lets a fresh agent with no memory of this conversation continue the work.
- Distinctive: line 15
Write to the project root of the current workspace:
- Very specific: line 20
Create the handoff/ directory if it does not exist.
- Distinctive: line 56
If the user passed arguments, treat them as the focus of the next session and tailor the document to that.
- Distinctive: line 64
Write the document immediately, before doing anything else.
- Distinctive: line 65
Keep it complete but economical — the remaining budget is small.
“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
Write a handoff document that lets a fresh agent with no memory of this conversation continue the work. Assume the next session may run under a different account, on a different machine, with no access to this transcript.
Where to save it
Write to the project root of the current workspace:
handoff/HANDOFF-<YYYY-MM-DD-HHmm>.md— the documenthandoff/HANDOFF-latest.md— a copy of the same content, always overwritten
Create the handoff/ directory if it does not exist. Use the repository root
(the directory containing .git) rather than the current subdirectory. Never
write to a system temp directory — the doc must survive the session ending and
be readable by another account.
handoff/ is added to the repo's .gitignore automatically by a PostToolUse
hook the first time you write a file there, so the documents stay local. Tell the
user it was ignored, and that if they want the document to travel between
machines (not just between accounts on one machine) they should commit the
folder instead.
What to include
- Task — what the user is trying to achieve, in their own framing.
- State — what is done, what is in progress, what is untouched. Be specific about which parts are verified versus assumed.
- Key decisions and the reasons — especially ones a fresh agent would otherwise re-litigate or accidentally reverse.
- Next steps — concrete and ordered. First item should be immediately actionable.
- Do not redo — things already tried that failed or were rejected, so the next session does not waste the budget repeating them.
- Environment — branch, uncommitted work, running services (ports), how to start them, credentials the user must supply themselves.
- Suggested skills — skills the next agent should invoke.
What to leave out
- Anything already captured in commits, diffs, specs, plans, ADRs or issues — reference those by path, SHA or URL instead of restating them.
- Secrets. Redact API keys, passwords, tokens, connection strings and personal data. Name the variable, never the value.
- Narration of the conversation. Write the current state, not a chat log.
Arguments
If the user passed arguments, treat them as the focus of the next session and tailor the document to that. Otherwise cover the work in progress broadly.
When invoked automatically
A Stop hook injects a request to run this skill once session usage crosses the
threshold (default 90%). In that case:
- Write the document immediately, before doing anything else.
- Keep it complete but economical — the remaining budget is small.
- End your turn by telling the user the path, their usage percentage, and that they can resume in a fresh session (or on another account) from that file.
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.