handoff-codex
Skill27 starsChanged 3 months agoMITView on GitHub
Use when the user asks for a handoff, session summary, context packet, continuation note, or wants another agent or future session to pick up the current work.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- claude-world/director-mode-litetheir own version, first seen Nov 1, 2026
- ulpi-io/plugin-handofftheir own version, first seen Jul 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- claude-world/director-mode-lite★ 80same name
- ulpi-io/plugin-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 repository16 other files it gives its agents.
- adversarial-plan-review-codexSkill
- canvas-design-codexSkill
- code-intelligenceSkill
- code-mapper-skillSkill
- deep-planning-codexSkill
- document-handoffSkill
- docx-winSkill
- frontend-design-codexSkill
- grill-me-codexSkill
- grill-with-docs-codexSkill
- pptx-winSkill
- repo-map-codexSkill
- ultraplan-codexSkill
- verification-plan-codexSkill
- web-artifacts-builder-codexSkill
- xlsx-winSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 10
Write a concise handoff document so a fresh agent or future session can continue the work without rereading the whole conversation.
- Distinctive: line 16
Use the operating system temporary directory only when the active instructions explicitly permit it.
- Distinctive: line 18
After writing the file, tell the user its absolute path.
- Distinctive: line 23
Do not require or create a repository planning workfolder.
- Distinctive: line 24
If the current collaboration mode prohibits writes, return the complete handoff in conversation instead of writing a file.
- Distinctive: line 25
Keep the same redaction rules for every destination.
- Distinctive: line 29
Treat the user's invocation text as the intended focus of the next session.
- Distinctive: line 44
Do not duplicate content already captured in PRDs, plans, ADRs, issues, commits, diffs, or other artifacts.
- Distinctive: line 50
Do not commit, push, install dependencies, run migrations, or make implementation edits as part of writing a handoff.
≈ “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
Codex Handoff
Purpose
Write a concise handoff document so a fresh agent or future session can continue the work without rereading the whole conversation.
Destination
Save the handoff under the active session folder unless the user specifies another destination. For projectless sessions, follow the workstation policy for resolving the real Documents folder and creating a dated session folder.
Use the operating system temporary directory only when the active instructions explicitly permit it. Do not modify repository files for a handoff unless the user explicitly asks for a repo-tracked artifact.
After writing the file, tell the user its absolute path.
Native Plan Mode
- Include the current objective, next action, blockers, decisions, and validation gaps from the conversation and inspected artifacts.
- Do not require or create a repository planning workfolder.
- If the current collaboration mode prohibits writes, return the complete handoff in conversation instead of writing a file.
- Keep the same redaction rules for every destination.
Input Focus
Treat the user's invocation text as the intended focus of the next session. If the user gives no focus, infer it from the latest active task and call out that inference in the handoff.
Required Content
Include:
- next-session objective;
- current status;
- important decisions and assumptions;
- relevant files, branches, commits, PRs, issues, and URLs;
- commands already run and their important results;
- remaining tasks in recommended order;
- known blockers, risks, and validation gaps;
- suggested skills the next agent should invoke.
Do not duplicate content already captured in PRDs, plans, ADRs, issues, commits, diffs, or other artifacts. Reference those artifacts by path or URL instead.
Safety
- Redact API keys, passwords, tokens, private personal data, and other sensitive information.
- Preserve enough context to continue the work, but do not copy long private conversation passages.
- Do not commit, push, install dependencies, run migrations, or make implementation edits as part of writing a handoff.
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.