Seth Godin 分享让 AI 维护工作交接文档的提示词
Create a handoff doc
- 1Seth Godin 提出让 AI 日常维护一份交接文档,新人无需原作者即可接手工作
- 2作者给出一段可直接复制的提示词,设 9 个固定板块,覆盖项目现状、文件位置、决策与待解问题
- 3提示词要求区分作者原话与 AI 推断并记录决策理由,每次有变化的会话结束前自动更新文档
- 4人工维护此类文档耗时难坚持,作者建议把提示词与文档一并存入常驻指令,每次会话自动加载
AI 把过去没人愿意坚持的交接文档变成可自动维护的常态,工作可移交性从个人自律变成一次性配置。
- 影响:岗位交接不再依赖当事人记忆,关键人员流动的风险随之降低;决策与假设被留痕,回头复盘和把工作迁去其他平台的阻力都会减小。
- 参考:可考虑选一个进行中的项目试运行这份 9 板块交接文档,重点记录决策理由与未验证假设;值得把提示词放进常驻指令,并定期核对 AI 标注的推断是否可信。
- 依据:判断基于作者给出的完整提示词与运行规则,属个人方法主张,无实测数据或独立验证。
Imagine if your job required you to maintain an updated handoff doc, something the boss could give to a new hire that would let them immediately get caught up on the work. All the file names, locations, assumptions, choices, dilemmas and contacts, organized and ready to go.
Creating something like this would be annoying and time consuming, and eventually we’d get very little done. In addition, we like leaving our intuition a bit unexamined and our choices somewhat undocumented.
But…
This is something your AI should be very good at. Clarity, documentation, commented analysis, all there, every day, an ongoing roadmap that makes it easier to unwind activities or transfer them to a different platform. Here’s a prompt you can cut and paste into the AI you use the most:
Maintain a handoff doc for this work. Its reader is a smart stranger
who has to take over tomorrow with no access to me or to our chats.
At the end of any session where something changed, update the doc before
you finish, without being asked. If nothing changed, say so in one line.
The doc has these sections, always in this order:
1. WHAT THIS IS — two or three sentences: the project, who it's for,
what "done" looks like.
2. CURRENT STATE — what works, what's half-built, what's broken. Dated.
3. WHERE THINGS LIVE — every file, folder, account, URL, and tool, with
the exact name and location. No "the spreadsheet." Name it.
4. DECISIONS — each choice we made, the alternatives we rejected, and why.
Never delete a decision; if we reverse one, mark it superseded and
note the date and reason.
5. ASSUMPTIONS — things we're treating as true but haven't verified.
Flag which ones would hurt most if wrong.
6. OPEN QUESTIONS & DILEMMAS — unresolved tensions, stated plainly,
with the leading options.
7. PEOPLE — who's involved, their role, how to reach them, what they're
waiting on.
8. NEXT STEPS — the first three things a newcomer should do.
9. HOW TO UNWIND — what it would take to stop, hand off, or move this
to another platform.
Rules:
- Distinguish what I told you from what you inferred. Mark inferences.
- Record the reasoning, not just the outcome. The "why" is the valuable part.
- Be specific enough that someone could act without asking a question.
- If something I say contradicts the doc, point it out instead of
silently changing it.
- Keep it tight. Cut stale detail into a dated one-line summary rather
than letting the doc bloat.
- If you're unsure whether something belongs, include it under
Open Questions.The prompt needs a permanent home: put it in stored instructions (along with the doc itself), so it loads every time instead of depending on you to paste it.
Over time, the document will get larger, but that’s okay, it’s better than not having it.
来源:Seth Godin · seths.blog