handoff
Skill2 starsChanged 3 months agoMITView on GitHub
Compact the current conversation into a handoff document another session or agent can resume from. Use when wrapping up with unfinished work, when context is getting long, or when the user says "hand this off", "write a handoff", or "save state for the next session". Produces a single Markdown file at a durable, harness-agnostic path and reports it. Does NOT continue the work itself; it only captures state so a fresh session can.
191 other projects use a version of this, 79 of them edited.
Adopted by
Most recently taken up by
- xiaoxiaosrm/dsh-mattpocock-skillsedited, 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-configedited, first seen Nov 8, 2026
- domengabrovsek/claudeedited, 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 · 79
- mattpocock/skills★ 309k18% same
- QuivrHQ/quivr★ 40k19% same
- The-Vibe-Company/quivr★ 40k19% same
- GreyDGL/PentestGPT★ 16k21% same
- ArcReel/ArcReel★ 6.3k18% same
- withcoral/coral★ 4.9k18% same
- bestofjs/bestofjs★ 3.1k20% same
- compozy/compozy★ 2.9k19% same
- bholmesdev/hubble.md★ 1.5k21% same
- CelestoAI/SmolVM★ 1.2k19% same
69 more not listed
Wrote their own version · 112
- ykdojo/claude-code-tips★ 10ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- davidondrej/skills★ 4.3ksame name
- feiskyer/claude-code-settings★ 1.7ksame name
- skforecast/skforecast★ 1.5ksame name
- openclaw/agent-skills★ 1.1ksame name
- suboss87/FDEOps★ 940same name
- JordanCoin/codemap★ 710same name
102 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 repository12 other files it gives its agents.
- buildSkill
- decision-coachSkill
- grill-with-docsSkill
- harness-configSkill
- logic-prototypeSkill
- paper-prototypeSkill
- polish-fixSkill
- post-build-reviewSkill
- pre-build-reviewSkill
- prototypeSkill
- wrapupSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 172 edited versions we read keep these.
4
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 15
Keep it short and skimmable.
- Distinctive: line 31
Do not duplicate content already captured in other artefacts (PRDs, plans, ADRs, issues, commits, diffs).
- Distinctive: line 39
If the invocation included a focus (arguments or an accompanying instruction), tailor the document to it.
- Very specific: line 54
If the goal or the invocation arguments suggest a short topic slug, insert it before the timestamp — handoff-<slug>-YYYYMMDD-HHMMSS.md.
- Distinctive: line 57
Write the document to that path and print it as the final step.
“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
A handoff is a single Markdown document that lets a fresh session, on any agent or harness, resume this work without re-reading the whole conversation. Capture the current state and the next move, not a transcript.
What to capture
Keep it short and skimmable. Include only what the next session actually needs:
- Goal — what we are trying to achieve, in a sentence or two.
- State — what is done, what is in progress, what has not been started.
- Next step — the single most concrete thing to do next.
- Key decisions — choices already made and why, so they are not relitigated. Attribute each one: confirmed by the user, an agent assumption (say so), or recorded elsewhere (link the PR/ADR/doc). Ideas only discussed are not decisions; they belong under open questions.
- Open questions and gotchas — blockers, risks, and anything surprising.
- Where to resume — the exact files, paths, commands, or URLs to pick up from.
- Previous handoff — if this session resumed from one, link it rather than re-summarising it; each re-synthesis loses fidelity and provenance.
- Suggested skills — the skills the next session should invoke, by name.
Do not duplicate content already captured in other artefacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact secrets and personal data — API keys, tokens, passwords, PII. The document lands in a durable, greppable directory and outlives the session, so anything leaked into it persists.
If the invocation included a focus (arguments or an accompanying instruction), tailor the document to it.
Saving the document
Save to a durable, harness-agnostic location, then report the full path back to the user so both they and the next session can open it:
dir="${HANDOFF_DIR:-$HOME/handoffs}"
mkdir -p "$dir"
path="$dir/handoff-$(date +%Y%m%d-%H%M%S).md"
echo "$path"If the goal or the invocation arguments suggest a short topic slug, insert it
before the timestamp — handoff-<slug>-YYYYMMDD-HHMMSS.md; the plain timestamp
form is the fallback.
Write the document to that path and print it as the final step.
$HANDOFF_DIR lets any environment redirect handoffs without editing the skill.
The default keeps them out of your project repos, survives reboots and temp-directory
cleanup, and names them so they sort chronologically and are easy to find and grep.
Credits
Derived from Matt Pocock's MIT-licensed handoff skill
(github.com/mattpocock/skills); upstream
licence in LICENSE-upstream.
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.

