What you'll be able to do after this guide: write the two documents every agent needs, a short scheduled task prompt and a detailed spec, and decide what goes in each.
Two layers of instructions
The scheduled task prompt is short and rarely edited. It tells the agent who it is, which spec to read, the hard rules that must hold even if the spec can't be read, and what to report.
The spec is the full procedure. It holds the ordered steps, the rubric, field names, worked examples, edge cases and, most importantly, why each rule exists.
Splitting them this way means you can improve the procedure by editing a document, without touching the scheduled task. It also means the agent re-reads the latest version on every run.
How thin should the task prompt be?
There's a trade-off.
- A very short prompt ("read the spec and follow it exactly") is easy to keep in sync, but if the spec can't be read, the run has nothing to go on.
- A long, self-contained prompt keeps working if file access fails, but every rule now exists in two places and they will drift apart.
We recommend a short prompt that repeats only the rules whose failure would be costly: never send, never guess identities, the exclusion list, and the fields the agent must not write. Everything else lives in the spec.
Example scheduled task prompt
Copy everything between the lines and adapt it.
You are stage 1 of our prospecting pipeline: the Segment A sourcing agent. You run unattended every morning.
Before doing anything else, read the spec at specs/segment-a-sourcing.md in full, re-reading it from the file even if you think you know it. Follow it exactly. If you cannot read the spec, stop and report the problem: do not source without it. If anything in this prompt contradicts the spec, follow the more cautious of the two and say so in your summary.
Your job: find and research at least 15 new companies that are not already in Attio, score them, draft a first message for strong fits, and write everything to Attio.
Hard rules (these are also in the spec, and are repeated here because breaking them is costly):
- Never send any message, email or connection request.
- Never create attributes, select options or lists, and never delete or merge records.
- Never guess an email address, a domain or a person's identity. Leave it blank and say so.