whats-next
Skill93 starsChanged 4 months agoMITView on GitHub
Write or refresh HANDOFF.md - a compact resume point holding completed objectives, live file paths, approaches already tried and rejected, and the exact next steps, placed against the roadmap in docs/ROADMAP.md. Use before /compact or /clear, at the end of a task block, when the context window crosses ~50%, or when asked "what's next", "where were we", "hand this off", or "resume".
16 other projects use a version of this.
Adopted by
Most recently taken up by
- MatthewDelprado/claude-skillstheir own version, first seen Nov 16, 2026
- TidalPaladin/skillstheir own version, first seen Nov 8, 2026
- jackneil/claude-jackedtheir own version, first seen Nov 5, 2026
- aantoniadis/skillstheir own version, first seen Nov 1, 2026
- aayushchugh/skillstheir own version, first seen Nov 1, 2026
- TanKaizokuO/claude-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use handoff.
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.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- WellApp-ai/skills★ 9same name
- aayushchugh/skills★ 4same name
- postmeridiem/clide★ 4same name
- wyattjoh/skills★ 3same name
- jackneil/claude-jacked★ 2same name
- alabenkhlifa/dayjob★ 1same name
- cacardinal/laila★ 1same name
- DavoDC/claude-playbook★ 1same name
- luw2007/skills★ 1same name
- TidalPaladin/skills★ 1same name
6 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 repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- coverage-reportSkill
- docs-passSkill
- new-packageSkill
- releaseSkill
- spikeSkill
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 14 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
- Very specific: line 20
Read the Open items section of docs/ROADMAP.md and the file under internal/notes/roadmap/ for the item in hand, when its row links one.
- Distinctive: line 26
Add what only this session knows: what you actually changed, and what you tried that did not work.
- Distinctive: line 29
If the session is thin on state - resumed, compacted, or you were handed a HANDOFF.md rather than doing the work - do not read packages …
- Distinctive: line 70
Every line is a permanent tax on it.
- Very specific: line 79
If an open item has been delivered, say so.
- Distinctive: line 81
No conversation summary, no restatement of the plan, no preamble.
“Common” is measured: kept by at least 6 in 10 of the 14 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
/whats-next
Produce HANDOFF.md at the repo root: everything needed to resume this work in a
fresh session and nothing else. It will be read cold, by a session with no
memory of this one. Optimise for that reader, not for a record of what happened.
Gather
One batch, then stop:
git status --short && git log --oneline -8Read the Open items section of docs/ROADMAP.md and
the file under internal/notes/roadmap/ for the item in hand, when its row links
one. That is the source
of truth for what "next" means. Never invent a roadmap position from the
conversation.
Add what only this session knows: what you actually changed, and what you tried that did not work.
If the session is thin on state - resumed, compacted, or you were handed a
HANDOFF.md rather than doing the work - do not read packages into this thread to
fill the gaps. Delegate one Explore subagent per unresolved question and
ask each for a one-line verdict plus file:line. The exploration stays in their
context window; only the verdict comes back.
Write
Overwrite HANDOFF.md with this shape. Omit a section that has no content -
never write "N/A" or "none".
# HANDOFF - <YYYY-MM-DD>
**Roadmap:** <open item> - <what remains of it>
**Branch:** <branch> @ <short sha> · <clean | n files dirty>
## Done
- <objective> - <where it landed>
## Live files
- [path](path) - <what is half-finished in it>
## Rejected - do not retry
- <approach> - <what broke>
## Next
1. <exact command, or exact edit to an exact path>
## Open questions
- <question> - <what decides it>Rules
- Hard cap ~60 lines. This file is loaded at the start of the next session. Every line is a permanent tax on it.
- Next steps are commands and edits, not intentions. "Add
token()andinject()topackages/core/src/di/, resolving through a module-levelcurrentInjectorset around eachnew Klass()" - not "continue DI work". - Rejected is the highest-value section. It is the only content a fresh session cannot re-derive from the tree. Record the approach, the symptom, and the path it lives or lived in. Rejections already written down in docs/architecture/ belong there, not here - link, don't copy.
- Paths as clickable relative markdown links.
- If an open item has been delivered, say so. If docs/ROADMAP.md is stale, fix that doc - do not record the drift in HANDOFF.md.
- No conversation summary, no restatement of the plan, no preamble.
After writing
State the path and the roadmap position in one line, then name the next move:
- same subtask, context heavy →
/compact, and say explicitly what to preserve - switching subtask →
/clear, thencontinue from HANDOFF.md
HANDOFF.md is gitignored. It is session state, not a repo artifact - rewrite it
freely.
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.

