handoff
CLAUDE.md0 starsChanged 4 months agoMITView on GitHub
Use the Handoff workflows in skills/handoff/SKILL.md, skills/handon/SKILL.md, and skills/handoff-handon/SKILL.md. When the user says /handoff, "handoff", "prepare a handoff", or indicates they are ending a work session: When the user says /handon, "handon", "continue from last time", or asks to restore context: Never write secrets, credentials, .env values, private keys, or production configuration into handoff files.
- Reads credentials
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- handoff-handonSkill
- handoffSkill
- handonSkill
The file
We split this CLAUDE.md into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Use the Handoff workflows in skills/handoff/SKILL.md, skills/handon/SKILL.md, and skills/handoff-handon/SKILL.md.
- Very specific: line 5
When the user says /handoff, "handoff", "prepare a handoff", or indicates they are ending a work session:
- Very specific: line 8
Follow the Handoff workflow.
- Very specific: line 10
Update docs/HANDOFF/TODO.md only when the task list changed or new follow-up work was discovered.
- Very specific: line 11
Update docs/HANDOFF/DECISIONS.md only when a durable project decision was made or confirmed.
- Very specific: line 13
When the user says /handon, "handon", "continue from last time", or asks to restore context:
- Distinctive: line 16
Follow the Handon workflow.
- Distinctive: line 18
Do not modify code until the user explicitly confirms.
- Very specific: line 20
Never write secrets, credentials, .env values, private keys, or production configuration into handoff files.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
Handoff
Use the Handoff workflows in skills/handoff/SKILL.md, skills/handon/SKILL.md, and skills/handoff-handon/SKILL.md.
When the user says /handoff, "handoff", "prepare a handoff", or indicates they are ending a work session:
- Read
skills/handoff-handon/SKILL.md. - Follow the Handoff workflow.
- Always update
docs/HANDOFF/CURRENT.md. - Update
docs/HANDOFF/TODO.mdonly when the task list changed or new follow-up work was discovered. - Update
docs/HANDOFF/DECISIONS.mdonly when a durable project decision was made or confirmed.
When the user says /handon, "handon", "continue from last time", or asks to restore context:
- Read
skills/handoff-handon/SKILL.md. - Follow the Handon workflow.
- Summarize the restored context first.
- Do not modify code until the user explicitly confirms.
Never write secrets, credentials, .env values, private keys, or production configuration into handoff files.
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.

