handoff
Skill1 starsChanged 14 days agoMITView on GitHub
把「还没做完的活」整成一张清单写进本条线的 交接.md,让下一个会话接着干(不是工作总结)。
191 other projects use a version of this.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- element-hq/element-calltheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- niki914/zafirotheir own version, first seen Nov 15, 2026
- davidondrej/skillstheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use decision-mapping, setup-ts-deep-modules and 9 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 47 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 59 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 105 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 101 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 62 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★ 325ksame name
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- GreyDGL/PentestGPT★ 16ksame name
- ykdojo/claude-code-tips★ 10ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 5ksame 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 repository6 other files it gives its agents.
- content-preflightSkill
- exploration-outsourcingSkill
- grill-meSkill
- writing-for-agentsSkill
- agents-md-auditSkill
- wait-whatSkill
The file
Files
交接
交接 = 一张「还没做完的活」的清单,不是工作总结。 它只在一种情况下存在:一个对话撞到上下文窗口、活没干完、只能开新对话 —— 下一个会话靠它接着干。做完的当场消去(去处 = 产物 / 归档 / 覆盖前留的那一份)。
写到哪
本轮那条线的目录下的 交接.md(通用线 / 规矩线 → 当前工作区的 活跃\交接.md),固定这个文件名,每次覆盖。
哪条线? 看工作区那份 AGENTS.md:有线清单表就按表(每条线一行:目录 / 它的规矩 / 它的本轮状态);只有文字说明、没有表就按文字里的目录约定判断(装了这个包的默认工作区 AGENTS 就是后者)。那儿没有要写的那条线、或判断不了 → 问用户一句(宁可问,别写错那份:写错等于把这条线的状态写进别线,两个会话读的是不同的文件)。
放工作区里、不放系统临时目录 —— 临时目录会被清理,交接就没了;固定名字也不会越攒越多。
先读本线上一次的交接
结构与表头以本条线上一次的 交接.md 为准 —— 先读它,别另起一套;本条线第一次写,就照工作区里已有的任一份(先看通用线 活跃\交接.md)。
覆盖前先把上一份里还没做完的逐条带过来,已经做完的当场消去。
硬检查优先于旧形状:工作区 AGENTS.md 的〈交接的硬检查〉(若有)和下面这几条,比上一次那份的旧构造优先。上一次那份若还带着「做到哪了(状态)/动过的文件(改了什么)」这类工作总结节,按硬检查改,不照抄。
硬检查
- 只列还没做完的活:接着干什么、按顺序(「下一步」就是第一条);做完的当场消去;⛔ 不写「本轮做了什么」。
- 给「文件路径 + 行数」:一张表,表头固定
| 位置 | 行数 | 是什么 |;行数含空行;表后必须有一行以「(行数一律」开头(工作区的文档体检工具靠它停表;没有工具就照这个口径手工核)。表里放这条线的常驻文件,不是本轮动过的。 - 过程记录进「工作日志」:同目录
工作日志-YYYY-MM.md,一行一件事 + 一个在盘上能核到的指针;只有「完成了一件活」或「改了口径 / 翻了旧说法」才写;日常增删不写,也不落快照(只有整份重写 / 大改结构之前落一张);按月分卷,过月把上一卷整份搬到归档那一侧、一个字不改(那一侧叫什么、在哪,按工作区自己的约定 —— 装这个包的工作区默认是存放\)。 - 只引路径,不复述内容:已经写进别处的,给路径让下一个 agent 自己去读 —— 复述等于造两份会各自过期的副本。 「定过的口径 / 别踩的坑」只收两类:会让人干错活的、有正本但位置反直觉的;提醒类不写;条目一有正本就删掉、只留指针。
- 脱敏:不写 API key / 密码 / 个人信息;涉及就写「见某路径」,不抄内容。
- 覆盖前留退路:交接日常增删不落快照,整份重写 / 大改结构之前落一张(放归档那一侧,退路写进文件头);覆盖规矩文件则按全局规矩先留一份。
要用户自己动手的
单独一节,写清只有用户能做的事:要用户打的 / 命令(对模型不可见的 skill 只能由用户调)、要拍板的、推仓库这类。
别写成「调用 skill 工具」 —— 模型看不见的 skill,那样写会失败;要写成给用户的动作。
如果 /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.

