🎯 How to delegate so agents nail it

The difference between “this squad is magic” and “it didn’t do what I wanted” is almost always the brief, not the agent. Great delegation here is the same skill as briefing a sharp new hire: goal, context, constraints, and what done looks like.

Bad: “Write a blog post about our product.”

Good: “Write a 900-word post for founders who’ve outgrown spreadsheets, arguing that ops automation is a hiring decision. Pull real numbers from our May growth doc in Docs. Match the voice of our last two posts. Done looks like: a draft in Docs with a title I’d actually click, ready for my edit pass - don’t publish anything.”

Four moves that upgraded that prompt:

Audience + angle

, not just topic - “for founders who’ve outgrown spreadsheets, arguing X”.

Point at your materials

Agents can read your Docs; “pull from the May growth doc” beats pasting numbers.

Constraints that matter

Length, voice, and the guardrail (don’t publish).

Done looks like

Where the output lands and what state it’s in.

💡 Tip: Say “open a ticket instead of guessing” whenever the work touches money, customers, or anything public. Agents treat it as law - the decision comes to My Tickets, and nothing embarrassing ships while you’re at lunch.

A reusable delegation template

[Goal — one sentence]. Context: [who it’s for / links to docs / what I already know]. Constraints: [length, voice, budget, deadline, what NOT to do]. If you hit a decision about [money/customers/direction], open a ticket. Done looks like: [artifact + where it lives + what state].

Level up: stop specifying, start briefing lanes. Once an agent nails a task twice, promote the instructions into its standing setup - the inbox briefing for email (Email → gear → Briefing), the schedule’s instructions for recurring jobs, or just tell the lead: “From now on, all competitor questions go to Atlas, and Atlas always cites sources.” The squad remembers. Your prompts get shorter every week - that’s the compounding.