handoff
Skill1 starsChanged 3 months agoMITView on GitHub
Write a durable engineering handoff for ongoing agent work: changed files, current goal, evidence, risks, blocked items, and restart prompt. Use before pausing, compacting context, switching tools, ending a long session, or using work-handoff.
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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-reviewSkill
- debugSkill
- domain-modelingSkill
- implementation-planSkill
- requirements-reviewSkill
- test-and-verifySkill
- webgl-scroll-siteSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 172 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Leave the next agent with enough truth to continue without archaeology.
- Distinctive: line 12
Do one job: serialize task state into a restartable text artifact.
- Distinctive: line 14
Treat files as memory and conversation as lossy.
- Distinctive: line 15
Do not fabricate timings, test results, metadata, or authorship.
- Distinctive: line 16
Keep the restart prompt executable.
- Distinctive: line 20
Use when pausing, switching from Codex to OpenCode or back, preparing a SITREP, ending a long task, or preserving context before compaction.
- Distinctive: line 48
Do not claim verification that did not run.
- Distinctive: line 50
Keep it concise enough to paste into a fresh session.
“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
Leave the next agent with enough truth to continue without archaeology.
Unix/Pi Contract
- Do one job: serialize task state into a restartable text artifact.
- Consume git status, diffs, commands, risks, and user intent; emit a concise handoff.
- Treat files as memory and conversation as lossy.
- Do not fabricate timings, test results, metadata, or authorship.
- Keep the restart prompt executable.
Use
Use when pausing, switching from Codex to OpenCode or back, preparing a SITREP, ending a long task, or preserving context before compaction.
Gather
Inspect:
- Current working directory and branch.
git status --shortand relevant diff summary.- Commands run and their outcomes.
- Files changed by this task.
- Known failures, blockers, and assumptions.
- User intent that must survive the handoff.
Output
Write or return:
- Goal.
- Current state.
- Changed files.
- Evidence.
- Risks and blockers.
- Next steps.
- Restart prompt.
Quality Bar
- Distinguish user changes from agent changes when possible.
- Do not claim verification that did not run.
- Include exact commands for the next proof.
- Keep it concise enough to paste into a fresh session.
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.

