Skip to content
UsecaseBoard
← All use cases
dev.toWork Handover

Interview yourself before drafting a job handover manual

At a glance

Morgan Vale tests a handover recipe that separates documented rules, interview answers, and unresolved guesses. This workflow is listed under Work Handover, Office Work, Documentation.

Agents / tools
AI chat assistant

SourceBuilding a tool for these workflows? See weekly rates.

What they did

1) Collect task lists, logs, old handover notes, templates, and FAQs; remove confidential information. Attach them to a fresh assistant chat. 2) Request up to 12 numbered interview questions about unwritten rules, stale information, exceptions, and personal know-how, each pointing to a file. Answer them, then request up to six follow-ups on vague or conflicting answers and answer those too. 3) Request the manual with a tag after every fact: [F: filename], [I: question number], or [?] for an inference. Your answers override old files. 4) Have the assistant check every tag and move unsupported lines into an Ask before acting section as questions. Review that section and the outdated-files list, update the original files, and ask one broad final question per section to catch omissions.

How it went

Across three synthetic runs, the interview recipe recovered 15, 14, and 14 of 15 rules correctly.

Worth knowing

The employee was simulated. Evidence tags cannot expose a stale rule nobody questioned.

Save ideas in this browser. Upvotes count across the board.

Prompt excerpt

No prompt excerpt was provided by the source.

Sponsored

CodeBuddy

Tencent Cloud AI coding assistant for IDE and CLI.

Try CodeBuddy ↗
Explore all →