context-handoff
Skill1 starsChanged 2 months agoMITView on GitHub
Preserve project continuity before ending a substantial task or session by updating current truth, verified progress, decisions, risks, blockers, and exact next actions without dumping noisy transcripts.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- voyager67/AgentFieldkittheir own version, first seen Nov 8, 2026
- hatemecha/skillstheir own version, first seen Nov 1, 2026
- timyeou1234/context-handofftheir own version, first seen Nov 1, 2026
- asta-nguyen/kamehadbtheir own version, first seen Oct 16, 2026
- vorteg/swagenticstheir own version, first seen Oct 13, 2026
- yuanJewel/skillstheir own version, first seen Oct 11, 2026
Used with
Projects with it also use systematic-debugging.
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.
OpenAISkillsystematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- asta-nguyen/kamehadb★ 14same name
- asta-nguyen/agent-devkit★ 4same name
- timyeou1234/context-handoff★ 2same name
- yuanJewel/skills★ 2same name
- newyounghe-design/context-handoff-skill★ 1same name
- SuperMate-Ai/SuperMate-Harness-System★ 1same name
- vorteg/swagentics★ 1same name
- aimasteracc/harness-kit★ 0same name
- djhyes/context-handoff★ 0same name
- hatemecha/skills★ 0same name
3 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 repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- agentic-uxSkill
- benchmarkSkill
- capability-routerSkill
- codex-adapterSkill
- create-prdSkill
- creative-direction-sprintSkill
- decompose-prdSkill
- design-criticSkill
- design-engineering-qualitySkill
- design-intakeSkill
- design-opsSkill
- design-system-auditSkill
- design-systemSkill
- design-tokensSkill
- discoverSkill
- harness-evolutionSkill
- interaction-designSkill
- loop-engineeringSkill
- parallel-planSkill
- performance-uxSkill
- polishSkill
- product-design-routerSkill
- project-onboardingSkill
- research-ledgerSkill
- responsive-auditSkill
- security-gateSkill
- self-improvement-loopSkill
- specialist-routerSkill
- strategizeSkill
- token-auditSkill
- user-needsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
4
Distinctive
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 before ending substantial work, after major merges, before compaction, or whenever another agent/session may continue.
- Distinctive: line 26
commit/PR if available.
- Distinctive: line 28
Never rewrite prior entries to make history look cleaner.
- Very specific: line 44
If an architectural choice is durable, create/update an ADR.
- Very specific: line 45
If a visual choice is durable, update DESIGN_DECISIONS.md.
- Distinctive: line 49
Do not paste chat transcripts, chain-of-thought, or full test logs into memory.
“Common” is measured: kept by at least 6 in 10 of the 11 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
Context handoff
Use before ending substantial work, after major merges, before compaction, or whenever another agent/session may continue.
Update CURRENT_STATE.md
Record only present-tense factual truth:
- what exists,
- what is deployed,
- what is verified,
- what remains incomplete.
Append PROGRESS.md
For each verified accomplishment:
- timestamp/date,
- task ID,
- requirement/acceptance IDs,
- change summary,
- evidence,
- commit/PR if available.
Never rewrite prior entries to make history look cleaner.
Rewrite HANDOFF.md
Keep it concise:
- current goal,
- completed,
- in progress,
- blockers,
- unresolved decisions,
- exact next action,
- verification status,
- relevant files.
Decisions
If an architectural choice is durable, create/update an ADR. If a visual choice is durable, update DESIGN_DECISIONS.md.
Anti-pattern
Do not paste chat transcripts, chain-of-thought, or full test logs into memory. Distill facts, decisions, and evidence.
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.