agentsclimarketplace
Sign in

Handoff

Skill mehrad-dm/mastermind/skills/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, when the context window is filling up on multi-day work, or when a long multi-step task starts re-covering ground it already finished. Not the project's decision history across weeks: that's `roadmap`.From its SKILL.md

Install
npx -y skills add mehrad-dm/mastermind --skill handoff

Assembled 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

2.5 KB, 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

  1. Goal: the outcome being built, in one line.
  2. State: Done / In-progress / Next, as a short checklist. Be honest about what's not verified.
  3. Key decisions & why: the non-obvious choices and their rationale (so they aren't relitigated).
  4. Map: where the relevant code/files/config live; the entry points.
  5. Gotchas: traps, failing things, env quirks, anything that bit you.
  6. How to resume & verify: the exact command(s)/check to pick up and confirm green.

Rules

Summarize and link, 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.

The ledger: for work that outlives one context window

A handoff is written once, at the pause. A ledger runs the whole way through: an append-only record of what has actually been completed, so a long task can lose its thread without losing its place. Start one when the work will be summarized more than once.

  • First line names the work: the plan, spec, or issue it belongs to. A ledger nobody can match to a plan is a page of orphaned sentences.
  • Append one line as each step completes: what was done, and the check that proved it. Earlier entries are never rewritten or tidied: it is a record of what happened, not a plan of what will.
  • Conversation memory does not survive compaction: trust the ledger and the git log over your own recollection, most of all when you feel certain. Re-doing finished steps is the costliest failure in long-horizon work, and it always arrives wearing "I remember doing that." Read the record, then act.

Same instinct as the episodic journal appended at each verdict (~/.mastermind/engineering/core/rigor.md), one level down: the journal spans tasks, the ledger spans steps inside one.

What ships with it: 1 file

4.7 KB alongside SKILL.md

Gives 0 of the 12 instructions most agent orchestration skills give

Counted across 848 of the 1,300 authors here whose files we hold, read 2026-09-06

  • Dispatch one agent per independent problem domainin 56 of 848, across 42 files
  • Run full test suite after integrationin 55 of 848, across 42 files
  • Verify fixes do not conflictin 40 of 848, across 32 files
  • Review each summary when agents returnin 40 of 848, across 31 files
  • Write a handoff document summarising the current conversationin 30 of 848, across 25 files
  • Reference existing artifacts by path or URLin 26 of 848, across 24 files
  • Give each agent a specific scopein 19 of 848, across 10 files
  • Give each agent a clear goalin 19 of 848, across 10 files
  • Include a suggested skills section in the documentin 18 of 848, across 16 files
  • Tailor the doc to the user argumentsin 18 of 848, across 15 files
  • Issue all subagent dispatches in the same responsein 17 of 848, across 11 files
  • Use git worktrees for isolationin 17 of 848, across 8 files

Said here and by no other author read

  • Capture the goal in one line
  • List state as a checklist
  • Map relevant code and files
  • Note gotchas and environment quirks
  • Provide commands to resume and verify
  • Summarize and link to details

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 626,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.