agent-handover
Skill0 starsChanged 10 days agoMITView on GitHub
Start, resume, or conclude substantial cross-session work while preserving a concise, redacted handover and a concrete next action.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- harshnag/agent-engineering-practicestheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- harshnag/agent-engineering-practices★ 0same name
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 repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- brand-sweepSkill
- design-tokensSkill
- experiment-labSkill
- parity-checkSkill
- pitch-from-evidenceSkill
- plan-and-buildSkill
- platform-reachSkill
- product-kickoffSkill
- product-reconSkill
- quality-loopSkill
- repository-auditSkill
- review-miningSkill
- review-practiceSkill
- security-auditSkill
- stack-foundationSkill
- systematic-debuggingSkill
- technical-reconSkill
- ux-qualitySkill
- web-qualitySkill
- agent-handoverSkill
- brand-sweepSkill
- design-tokensSkill
- experiment-labSkill
- parity-checkSkill
- pitch-from-evidenceSkill
- plan-and-buildSkill
- platform-reachSkill
- product-kickoffSkill
- product-reconSkill
- quality-loopSkill
- repository-auditSkill
- review-miningSkill
- review-practiceSkill
- security-auditSkill
- stack-foundationSkill
- systematic-debuggingSkill
- technical-reconSkill
- ux-qualitySkill
- web-qualitySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when work may cross a session, branch, machine, model, or owner.
- Very specific: line 13
Check directly for root HANDOVER.md.
- Distinctive: line 17
Treat the working tree and current repository state as authoritative when they disagree.
- Distinctive: line 23
Keep the handover limited to state another actor cannot reconstruct from Git: current goal, decisions, validation, blockers, and the next …
- Very specific: line 29
Run make handover to create root HANDOVER.md from ../../../docs/handoffs/TEMPLATE.md with the git facts pre-filled (it never overwrites an …
- Distinctive: line 32
Update every section concisely and remove stale claims.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent handover
Use this skill when work may cross a session, branch, machine, model, or owner. For a short self-contained change, use the normal issue and verification loop.
Start or resume
- Check directly for root
HANDOVER.md; read it completely if present. A hooked host already printed it in the session brief (make startotherwise), and.agent/checkpoint.mdholds the last pre-compaction snapshot. - Compare it with the current branch, working tree, manifest, and linked issue. Treat the working tree and current repository state as authoritative when they disagree.
- Preserve unrelated uncommitted changes and secrets boundaries.
While working
Keep the handover limited to state another actor cannot reconstruct from Git: current goal, decisions, validation, blockers, and the next concrete action. Reference issues, commits, specs, and ADRs instead of copying them.
Conclude or pause
- Run
make handoverto create rootHANDOVER.mdfrom../../../docs/handoffs/TEMPLATE.mdwith the git facts pre-filled (it never overwrites an existing one). - Update every section concisely and remove stale claims.
- Use
../../../docs/handoffs/TEMPLATE.mdfor a committed cross-machine handoff, then add it to the docs index. - State in the final response whether the handover was updated and what remains.
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.

