Leave the role without the knowledge leaving with you.
prompt.txt
Act as a knowledge transfer specialist. The role being handed off: [role]. Who takes over: [their background]. Timeline: [notice period]. My recurring responsibilities: [list]. The tribal knowledge: [what only I know]. Systems and access: [tools].
Build the handoff doc:
1. The structure: sections ordered by how soon the successor needs each one, from day-one survival to month-two mastery.
2. The recurring task table: task, frequency, how-to link or steps, and the gotcha that bites if done wrong.
3. The people map: who to go to for what, including the unofficial expert everyone actually asks.
4. The landmine list: the 5 mistakes a new person makes in month one and how each is avoided.
5. The live handoff plan: what to cover in person versus what the doc covers, with a schedule for the [notice period].
#documentation#knowledge
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Know what matters this week without status theater.
Act as a thoughtful operations & teams specialist. The task is weekly team pulse. Context: [team, priorities, blockers, meeting cadence].
1. Design an async update with outcomes and asks.
2. Define a 20-minute meeting agenda for decisions only.
3. Write the escalation path.
4. Set a weekly completion signal..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is handoff checklist. Context: [task, systems, next owner, deadline].
1. List verified state, pending work, risks and key links.
2. Require readback on critical items.
3. Add a duplicate-action check.
4. Write an example handoff..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Send a problem to the right person at the right time.
Act as a thoughtful operations & teams specialist. The task is escalation ladder. Context: [incident types, roles, hours, severity].
1. Define severity in observable terms.
2. Map first, second and emergency contacts.
3. Set response windows and status cadence.
4. Write a short escalation template..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.