handoff
Skill410 starsChanged 5 months agoMITView on GitHub
Hand a written brief to an ACP agent that works in its own git worktree and herdr workspace, then check its work before anyone merges it. Writes a dated handoff doc, creates a beads epic when the repo has one, cuts a `handoff/<id>-<slug>` branch from the current branch, launches the agent through herdr''s `acp-run` (default `cmd acp`), and later verifies commits, stray changes and the brief''s checks. Use when the user says "hand this off", "create a handoff", "start it in its own worktree", "give this to an agent", "launch an agent on this epic", or wants an epic or multi-step to-do worked on away from a shared checkout. Requires git and a running herdr; beads is optional.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- xiaoxiaosrm/dsh-mattpocock-skillstheir own version, first seen Nov 8, 2026
- ethosagent/ethostheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- anombyte93/prd-taskmastertheir own version, first seen Nov 8, 2026
Used with
Projects with it also use decision-mapping, setup-ts-deep-modules and 10 more.
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.
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 8 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 42 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 93 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 87 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 51 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 54 projects that use this
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- mattpocock/skills★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- GreyDGL/PentestGPT★ 16ksame name
- ykdojo/claude-code-tips★ 10ksame name
- ArcReel/ArcReel★ 6.3ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- withcoral/coral★ 4.9ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
181 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 repository120 other files it gives its agents.
- automation-advisor/CLAUDE.mdCLAUDE.md
- agency-docs-updaterSkill
- agency-meetup-publishSkill
- agency-socialsSkill
- agent-cliSkill
- agent-roundtableSkill
- app-mapSkill
- app-releaseSkill
- automation-advisorSkill
- background-agentsSkill
- balancedSkill
- brand-agencySkill
- browser-mateSkill
- browsing-historySkill
- chrome-historySkill
- cms-migration-checklistSkill
- coaching-session-summarizerSkill
- codexSkill
- cognitive-toolkitSkill
- context-builderSkill
- cull-release-checkSkill
- cull-release-prepareSkill
- cull-release-publishSkill
- cull-release-recoverSkill
- cull-releaseSkill
- cull-release-verifySkill
- cullSkill
- daydreamSkill
- decision-to-deliverySkill
- decision-toolkitSkill
- deep-researchSkill
- design-tokensSkill
- doctorgSkill
- ecosystemSkill
- elevenlabs-ttsSkill
- elimination-researchSkill
- fathomSkill
- feature-factorySkill
- firecrawl-apiSkill
- firecrawl-researchSkill
- font-featuresSkill
- github-gistSkill
- gmailSkill
- google-image-searchSkill
- gpt-image-2Skill
- granolaSkill
- gwsSkill
- health-dataSkill
- herdr-orchestratorSkill
- i18n-studioSkill
- init-tauri-appSkill
- init-xcode-appSkill
- insight-extractorSkill
- jtbdSkill
- lab-retroSkill
- learning-vaultSkill
- linearSkill
- llm-cliSkill
- local-modelsSkill
- meeting-prepSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 172 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Run them from inside the target repository.
- Very specific: line 31
Write the doc: Use handoff new "<title>" or the project's own convention: look at existing handoff or spec docs first and match their …
- Very specific: line 45
Close: after the merge: handoff close ID removes the worktree and workspace, deletes the merged branch and closes the epic.
- Distinctive: line 61
Only ACP agents. The script never falls back to a TUI agent.
“Common” is measured: kept by at least 6 in 10 of the 172 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
Handoff
A handoff is a dated doc plus, when the repo uses beads, an epic. The doc is the brief. A
session or agent starts only when the user says to start it. scripts/handoff does every
mechanical step; the agent's job is to write a good doc and report what the script prints.
Commands
scripts/handoff new "Report importer" # docs/YYYY-MM-DD-report-importer-handoff.md
scripts/handoff start DOC # epic + worktree + launch, detached
scripts/handoff start DOC --supervise # wait for the agent, then collect
scripts/handoff start DOC --here # worktree, branch, brief and epic; no agent
scripts/handoff start DOC --agent "codex-acp" # any ACP agent command
scripts/handoff status ID # commits, dirty files, agent exit, log tail
scripts/handoff collect ID # verify and record the result on the epic
scripts/handoff close ID [--discard] # remove the worktree once merged
scripts/handoff listRun them from inside the target repository. State is kept in <git-common-dir>/handoff/<id>/
(state.json, brief.md, run.log), so nothing is added to the working tree.
Workflow
- Write the doc. Use
handoff new "<title>"or the project's own convention: look at existing handoff or spec docs first and match their folder and naming. Fill in problem, scope, what is out of scope and "done when". Put verification commands in a fenced block under a heading namedChecks(orVerify):collectruns each line in the worktree. - Stop and wait until the user says to start it. Writing the doc is not consent to launch.
- Start.
handoff start DOCprints the base branch and commit it cuts from; relay that line, and any note that the source checkout has uncommitted changes the worktree won't have. Withoutbdor a.beads/folder the epic is skipped with a one-line note. - Check in with
handoff status ID. Don't poll in a loop; use--supervisewhen the user wants to wait for it. - Collect.
handoff collect IDchecks that the agent finished, the branch has commits, the worktree is clean, nothing new changed in the source checkout, and each brief check passes. It records the result as a comment on the epic and exits non-zero on any failure. - Merge is the user's call. Report the verdict and the branch name, then stop.
- Close after the merge:
handoff close IDremoves the worktree and workspace, deletes the merged branch and closes the epic. It refuses an unmerged branch unless--discard, which removes the worktree but always keeps the branch.
What the agent is told
The doc is sent as the prompt with fixed rules appended: stay in the worktree, commit on the
handoff branch with explicit paths only, never merge, rebase, push or open a PR, don't touch
files outside the worktree, report blockers instead of working around them, and end with a short
report. acp-run enforces the path rule for permission requests and file reads and writes.
Requirements and limits
- git, Python 3, a running herdr, and herdr's
acp-runscript. The script looks foracp-runonPATH, next to this skill in a siblingherdrskill, and in the usual skill folders; setHANDOFF_ACP_RUNto override. - Only ACP agents. The script never falls back to a TUI agent.
- The worktree is cut from committed history. Uncommitted changes, including an uncommitted doc, aren't in it; the brief still reaches the agent because it is passed as a file.
- "Nothing changed outside the worktree" compares the source checkout's
git statuswith a snapshot from start time. In a checkout shared with other sessions a change there may be theirs, socollectnames the files instead of guessing.
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.

