handon
Skill1 starsChanged 4 months agoMITView on GitHub
Use when a paused frontend, backend, or integration workstream must resume from its sidecar TRACK.md and HANDOFF.md records.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kev1nzh37/handofftheir own version, first seen Jul 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kev1nzh37/handoff★ 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- electron-debugSkill
- electron-implementationSkill
- electron-ipc-securitySkill
- electron-releaseSkill
- electron-reviewSkill
- electron-test-e2eSkill
- github-deliverySkill
- handoffSkill
- making-thingsSkill
- mts-moreSkill
- mts-oneSkill
- mts-splitSkill
- product-prdSkill
- solution-architectureSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 23
Do not use a token, hidden authority transfer, task-level handoff, or automatic Git action.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Hand On
Resume a whole paused workstream in any supported host while preserving its current TDD task.
- Require explicit user direction and read the sidecar project, paused
TRACK.md,HANDOFF.md, currentTASK.md, and contract. Reject a track that is notPAUSEDor a missing/incomplete handoff. - Require user confirmation that the receiving parent Agent has created or entered the branch and relative worktree declared in TRACK.md. Do not discover, create, or select it automatically.
- Record the receiving host, parent identity, and date in TRACK.md. Change
the track status to
ACTIVEwithout changingcurrent_task. - Report the resumed task, next TDD action, validation debt, contract impact,
and risks from the handoff. Route implementation to
mts-oneor, only if capability evidence permits,mts-more.
Do not use a token, hidden authority transfer, task-level handoff, or automatic Git action.
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.