The Handover Doc | Master AI Automation in 4 hours Master AI Automation in 4 hours Course About Ayush Modules Sample chapter Toolbox The Microcap Minute Classroom / Module 07: The AI Relay Team / Chapter 3 The Handover Doc Watch first, then read. Same lesson, your pace. What you will learn – The template this course uses for every handover – Why “reviewable by anyone” is the design goal – Storing handovers so projects stay auditable The template Save this to prompts/handover-template.md today; use it forever: # HANDOVER, [project name] · v[n] · [date] ## 1. GOAL (unchanged since v1) ## 2. CONSTRAINTS (standing) – Audience: … – Format/length: … – Tone: … – Hard limits: … ## 3. ARTIFACT UNDER REVIEW / TO EXTEND <<>> ## 4. YOUR TASK (this leg only) ## 5. DO NOT – – ## 6. OUTPUT CONTRACT Return: Six sections, five minutes to fill, and it works identically whether the receiver is Qwen, Claude, Kimi, OpenAI, or a human classmate at midnight. That last property is deliberate: a handover a human can review is a handover you can trust. If your baton only makes sense to machines, you’ve built something unauditable, which is how errors hide. Why the contract matters Section 6 is the secret weapon. Demanding “revised text + 3-bullet change log” forces the receiver to expose its edits, you see exactly what moved without diff-reading two versions. For review legs: “verdict PASS/FAIL + numbered issues with severity” . Contracts turn vibes into checkable outputs. Filing Handovers compose into an audit trail. Keep one folder per project: projects/newsletter/ h01-draft.md ← Qwen’s draft leg h02-review.md ← Claude’s review leg h03-final.md ← OpenAI’s polish leg Each file is a filled template. Six months later you can reconstruct every decision, or hand the whole folder to a newcomer who reads their way to competence. Teams at real companies run on worse documentation than this. Try it yourself Take any real task from this week. Run it through three AIs using filled templates per leg (draft → review → polish across Qwen → Claude → OpenAI). File all three handovers in a project folder. Then the acid test: give the three files to a friend and ask what happened. Their comprehension is your quality score. Key takeaways – The six-part template: goal, constraints, artifact, task, verboten, output contract. – Human-reviewable = trustworthy; machine-only batons hide errors. – Output contracts force transparency (change logs, PASS/FAIL verdicts). – Filed handovers become your project’s audit trail and training manual. Download the exercise sheet (PDF) Module workbook (PDF) ← Prev: Relay racing Next: Full worked example → Classroom / Module 07: The AI Relay Team / Chapter 3 The Handover Doc What you will learn – The template this course uses for every handover – Why “reviewable by anyone” is the design goal – Storing handovers so projects stay auditable The template Save this to prompts/handover-template.md today; use it forever: # HANDOVER, [project name] · v[n] · [date] ## 1. GOAL (unchanged since v1) ## 2. CONSTRAINTS (standing) – Audience: … – Format/length: … – Tone: … – Hard limits: … ## 3. ARTIFACT UNDER REVIEW / TO EXTEND <<>> ## 4. YOUR TASK (this leg only) ## 5. DO NOT – – ## 6. OUTPUT CONTRACT Return: Six sections, five minutes to fill, and it works identically whether the receiver is Qwen, Claude, Kimi, OpenAI, or a human classmate at midnight. That last property is deliberate: a handover a human can review is a handover you can trust. If your ba
The Handover Doc
Written by
in