Two Claude Code sessions, one repo, and a protocol they helped write

Have you ever spent hours of work in a Claude session, realized you couldn’t use that same session for the next phase of the work, and still wanted everything you’d built up there? What if you could split the task across two agents — without having designed that capability into a preprompt up front? I want to walk you through a small piece of social engineering between me and two Claude Code sessions. It came in the form of a collaboration protocol defined in a markdown file. The file itself matters less than how it got written: the agents helped me write it while they worked. Here’s how it came together. Context was running out! I could see I was running myself into a corner with the complexity of the prompts I was providing. I was rewriting the opening of a workshop deck I’ve been building. (It’s an impress.js presentation, the kind where slides float around a 2D canvas instead of just paging.) The old opener had a “what if your terminal could think?” hook. I wanted a different…