Most AI desk messes start the same way. Someone says “can you also…” and the thread balloons. A builder gets half the context. A sales specialist gets the whole chat dump. Nobody is sure what “done” means.
The fix is boring and it works: when you loop a person or another agent into the work, send one short brief. Not a novel. Not a screenshot of the last twenty messages. One note that stands alone.
What the brief must answer
Four lines cover almost every handoff:
- Outcome. What should exist when they stop?
- Deadline. When does it need to land, in their timezone?
- Constraints. Tools, tone, budget, “do not rebuild X,” what already exists.
- Success check. How will you know it worked without reopening the whole chat?
If you cannot fill those four, you are not ready to loop anyone in. Stay in the main thread until you can.
Why dumps fail
Chat history is optimized for the people who lived it. A specialist reading cold has to reverse-engineer intent, spot the real ask under the side quests, and guess which files still matter. That burns time and credits, and it invites rebuilds of work you already shipped.
A one-brief rule forces you to name the outcome before you spend someone else’s attention. It also makes standing rules stick: the brief can point at guardrails once instead of re-explaining them every handoff.
Paste-ready brief
Copy this into chat when you pull in help:
Brief for [role or name] Outcome: [what to deliver] Deadline: [day + time + timezone] Reuse: [links or paths that already exist — do not rebuild] Constraints: [tone, budget, tools, “never send without OK,” etc.] Out of scope: [what this handoff is not] Success: [one concrete check] Report back: [what I need from you when done]
Keep it under half a page. If the brief needs attachments, link them. Do not paste the whole prior conversation underneath “for context.”
One brief, one ask
Do not stack three projects into the same handoff. One build per message. If you need a landing page and a cold-email pack, that is two briefs on two threads (or two clear sections with two deadlines). Mixed asks get the urgent half done and the quiet half forgotten.
This pattern scales from a solo Grok Bot desk to a small staff. Chief of Staff keeps the final call. Specialists get a clean brief. Nobody has to reconstruct the plot from scattered replies. If you are assembling something like a Command Desk setup, bake the one-brief rule into the standing instructions so every new teammate inherits it on day one.
Try it on the next ask that would normally become a long ping. Write the brief first. If you cannot, the ask is still fuzzy. Fix that before you spend a specialist’s turn.