task-handoff
Skill1 starsChanged 3 months agoMITView on GitHub
Use when a Codex task must continue in another task or session with verified context, explicit boundaries, and a compact privacy-safe handoff.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- PaulRBerg/dot-agentstheir own version, first seen Nov 6, 2026
- PaulRBerg/agent-skillstheir own version, first seen Oct 24, 2026
- aberson/skill-meshtheir own version, first seen Oct 24, 2026
- Peter537/peter537-agent-plugintheir own version, first seen Oct 11, 2026
- yearth/skillstheir own version, first seen Sep 8, 2026
- manwithshit/task-handofftheir own version, first seen Jul 4, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- PaulRBerg/agent-skills★ 104same name
- PaulRBerg/dot-agents★ 6same name
- yearth/skills★ 4same name
- aberson/skill-mesh★ 2same name
- manwithshit/task-handoff★ 0same name
- Peter537/peter537-agent-plugin★ 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 repository5 other files it gives its agents.
- development-plannerSkill
- execution-controllerSkill
- skill-routerSkill
- task-control-towerSkill
- verification-gateSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a continuation record from verified work, not a transcript dump.
- Distinctive: line 16
Verified completed: only outcomes supported by tests, diffs, commits, logs, or receipts.
- Distinctive: line 24
Do not include raw conversation by default.
- Very specific: line 26
Never invent a completed item, command result, path, commit, timestamp, or blocker.
- Distinctive: line 30
Read the latest verified artifact, status, and boundary notes.
- Distinctive: line 32
Remove everything not needed for the destination task's next safe action.
- Distinctive: line 34
Run a final privacy check before sharing or saving the handoff.
- Distinctive: line 36
Do not silently broaden scope, authorize external actions, or transfer secrets.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Task Handoff
Create a continuation record from verified work, not a transcript dump.
Required Fields
Include these sections in this order:
- Objective: the concrete outcome still being pursued.
- Current scope: files, modules, or behavior currently in bounds.
- Verified completed: only outcomes supported by tests, diffs, commits, logs, or receipts.
- Latest evidence: the newest inspectable evidence and when it was produced.
- Blocker or user action: the exact dependency, approval, or missing input.
- Frozen boundaries: behavior, data, files, or environments that must not change.
- Next safe step: one action the destination task can perform immediately.
Sanitization
Do not include raw conversation by default. Remove credentials, authentication material, private data, internal addresses, personal contact details, and unrelated history. Include identifiers only when explicitly requested and necessary for continuation. Prefer generic labels in examples.
Never invent a completed item, command result, path, commit, timestamp, or blocker. Mark unknown facts as unverified and state what evidence would resolve them.
Procedure
- Read the latest verified artifact, status, and boundary notes.
- Separate facts from assumptions.
- Remove everything not needed for the destination task's next safe action.
- Populate the required fields using short bullets.
- Run a final privacy check before sharing or saving the handoff.
Do not silently broaden scope, authorize external actions, or transfer secrets. A handoff communicates state; it does not grant permission.
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.