handofflisted

# /handoff — session resume note > **Only the user runs this.** It happens when they type `/handoff`, and at no > other time. If you are reading this file because *you* decided to — to see what > it does, or to carry out its steps yourself — then stop and do neither. > Following these instructions **is** running the skill, whichever route you took > to them, and a checkpoint the user did not ask for is one they will believe > happened when it did not. Say the skill exists and let them invoke it. When invoked, write a `TechnicalDirector.HANDOFF.md` at the project root that lets the **next** session resume this work with **zero prior context**. Invoking this skill is your authorization to do so. The filename is prefixed with this blueprint's name (`TechnicalDirector`) so multiple blueprints sharing one repo each keep their own handoff without clobbering each other. Write exactly `TechnicalDirector.HANDOFF.md`, no other name. A handoff is not a compact: after a `/clear` there is no conversation summary to fall back on, so `TechnicalDirector.HANDOFF.md` must be **fully self-contained**. Assume the reader boots fresh, has never seen this conversation, and reads only this file plus the pointers it names. `TechnicalDirector.HANDOFF.md` is **transient and untracked** — it is read on boot, then deleted. Begin the file with a one-line banner: `> Transient resume note (TechnicalDirector). Read on boot, then delete.` Write these sections, in order: 1. **Read first** — point the ne