Describe the Job in One Sentence With No "And"

Describe the job in one sentence, with no "and." Not "write the draft and post it." Just "write the draft." If there is another step, give it to another agent. One researches. One writes. One publishes. One job. One agent.

A long prompt with five "ands" is how you rebuild the one-person content team inside a model. Research, design, copy, analytics, timing, and publishing is six jobs. A bot with six jobs does not save you. It averages you.

This is the single sharpest rule from Scotty Beam's September 2026 field report on agent content teams, and it applies to human job descriptions just as well.

"And" hides a handoff you did not design. Write and post. Draft and send. Each "and" is a place where a bad signal should have died, and did not.

The field report is explicit about it: the first version gave a single "content agent" the jobs of researching, writing, and scheduling. The output was mediocre at everything. Splitting into narrow roles was the biggest quality jump in the whole experiment, and it was not close.

A single agent assigned "do all our social content" ends up mediocre at every sub-task because the context is always wrong. A 24/7 agent is useless if it creates 24/7 slop. "And" is how slop crosses the desk.

Say the output, not the vibe.

Bad: "Help with content." Bad: "Research trends and write posts and schedule them."

Good: "Drop ten sourced topics from the last seven days into this file." Good: "Write one post with one idea, in this voice, from this slate." Good: "Place finished packages on the calendar as drafts. Do not publish."

The publisher sentence is the one shops skip. They write "post it" because they are tired of being the clipboard. That "and post" is how the experiment's one bad week happened: two posts went out that their owner would not have sent. It is also how a documented incident unfolded in which a bot asked to read a post published one instead.

If publishing is in the sentence, it is not a writer. "Would we have sent this for the client?" is an approver's question. If the writer bot also presses publish, you have no place to ask it.

You do not need seven bots on day one. Break the "ands" you already live with. Split in this order: write the draft, land it as a draft on the calendar, approve. Approve is a human.

The strategy block can have commas. It is context, not a job. Paste it into every agent. The job itself remains one sentence, no "and."

If you hear yourself say "and then it just..." you have a second job. If the output is a live post, you have an approval, not a job for the same bot. The shape to aim for is 36 drafts queued, 0 published. The point is the zero.

Open the last prompt you used for "content." Count the "ands." Rewrite it as one sentence. Put every leftover verb on its own line. Those lines are other jobs. Write the draft. Stop.

When you want the jobs named, the calendar filling with drafts, and a human still asking whether the client should send it, talk to us.