Handoff
Use when work needs to survive losing context — before a /clear on a long task, when pausing something unfinished, when handing over to a teammate or the next session, or when the context window is filling up on multi-day work.From its SKILL.md
npx -y skills add mehrad-dm/mastermind --skill handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 267 tokens by cl100k_base, as published. Nobody here has run it
MasterMind — Handoff
Context is the fundamental constraint (~/.mastermind/engineering/core/agent-loop.md); a long task shouldn't lose its thread to a
reset. Capture just enough to resume cold — high signal, low tokens.
Capture
- Goal — the outcome being built, in one line.
- State — Done / In-progress / Next, as a short checklist. Be honest about what's not verified.
- Key decisions & why — the non-obvious choices and their rationale (so they aren't relitigated).
- Map — where the relevant code/files/config live; the entry points.
- Gotchas — traps, failing things, env quirks, anything that bit you.
- How to resume & verify — the exact command(s)/check to pick up and confirm green.
Rules
Summarize, don't dump — link or point to detail rather than pasting it. Write it where the next session
will look (HANDOFF.md, a scratch file, or the issue). Prune it when the work completes.
Output
A tight HANDOFF.md: goal, state checklist, decisions, file map, gotchas, resume+verify steps.
What ships with it: 1 file
4.7 KB alongside SKILL.md
- ABOUT.md4.7 KB