handoff
Skill1 starsChanged 12 days agoMITView on GitHub
Save a short handoff of the current work to knowledge/handoffs/CURRENT.md so a fresh session (after /clear or restart) can pick up where this one stopped. Use when the user says "handoff", "save context", "I'm going to clear", when a task finishes, or when switching topics.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- HiteSit/real-scientist-skillstheir own version, first seen Nov 15, 2026
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
- QiYueran-source/waymarktheir own version, first seen Nov 15, 2026
- xiaoxiaosrm/dsh-mattpocock-skillstheir own version, first seen Nov 8, 2026
- ethosagent/ethostheir 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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 172 edited versions we read keep these.
1
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
- Very specific: line 9
Write the state a fresh session needs to continue without re-deriving anything.
- Very specific: line 12
If knowledge/handoffs/CURRENT.md exists and covers a different topic or an older task, move it to …
- Very specific: line 14
Write knowledge/handoffs/CURRENT.md using the template below.
- Distinctive: line 15
Never write secrets: no connection strings with passwords, API keys, tokens, or private keys.
“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 the state a fresh session needs to continue without re-deriving anything. The plugin's SessionStart hook loads it automatically in the next session (in Claude Code also after /clear and after the conversation is compacted).
Steps
- If
knowledge/handoffs/CURRENT.mdexists and covers a different topic or an older task, move it toknowledge/handoffs/archive/<YYYY-MM-DD-HHMM>-<slug>.mdfirst. If it is the same ongoing task, update it in place. - Collect facts:
git branch --show-current,git status --short,git log --oneline -5, any dev servers or background runs still alive (ports, test shells), and what this conversation decided. - Write
knowledge/handoffs/CURRENT.mdusing the template below. Keep it under 60 lines. Use specific file paths, commands and decisions, not narrative. - Never write secrets: no connection strings with passwords, API keys, tokens, or private keys. Refer to them by env var name.
- Reply with one line:
Handoff saved to knowledge/handoffs/CURRENT.md. Safe to /clear.
Template
# Handoff: <topic>
Updated: <YYYY-MM-DD HH:MM> | Branch: <branch> | Last commit: <hash subject>
## Goal
<1-2 lines: what the user is trying to achieve and why>
## Done
- <finished item, with file paths / commits>
## In progress
- <what was being changed when we stopped; exact file and function>
## Next steps
1. <the very next action a fresh session should take>
2. ...
## Decisions (and why)
- <decision>: <reason / user's words>
## Open questions / blockers
- <waiting on user, credentials, approval, etc.>
## State to know
- Uncommitted: <files or "none">
- Running: <servers, ports, background tests or "nothing">
- Tests: <which ran, results, known failures>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.