PromptIntermediateGrok Bot basics

Grok Bot task brief prompts

Templates for delegating work to a Bot with the scope, boundaries and definition of done written down.

2 min read

A brief is worth writing down because you will reuse it, and because the act of writing the "come back to me" list is where you notice what you were assuming.

The handover check is the important one

Running the last prompt before a Bot starts costs a minute and catches the misunderstandings that are expensive later. If the summary that comes back is subtly different from what you meant: fix the brief, not the Bot.

Pair this with the access questions

A brief controls intent. It does not control capability: a Bot cannot be talked out of permissions it holds. See Connecting Bots to your tools safely for the half of this that lives in settings rather than in text.

What changes

Grok Bot is early and its approval and scheduling features are moving. Treat these as the durable shape of a brief and check x.ai/bot for what the product enforces for you today.

Copy-ready prompts

4 prompts. Open one to read it, or take the whole pack.

1General task briefAny job you are handing over for the first time.

Goal: <one sentence, checkable>

Inputs:
- <where the material is, name the exact source>

Do:
- <the actions you are authorising>

Come back to me before:
- sending anything to anyone outside the team
- spending or committing money
- deleting or overwriting anything shared
- <anything else specific to this job>

Done means: <the state of the world when you finish>

If you get blocked: stop and tell me what is blocking you. Do not
improvise around a missing input.

2Draft-only briefThe task ends in something irreversible and you are not ready for that.

Goal: <one sentence>

Prepare everything up to the final step and stop there. Specifically:
- Save as a draft; send nothing.
- Leave a one-line note per item explaining what you based it on.
- Flag any item where you were unsure, rather than picking one.

Done means: <n> drafts ready for me to review, nothing sent, nothing
changed anywhere else.

3Recurring task, written onceThe job will repeat and you want the brief to be reusable.

This is a recurring task. Run it <cadence>.

Goal: <one sentence>
Inputs: <source, and how to find the new items each time>
Do: <steps>
Skip: <items that should be left alone, and how to recognise them>
Come back to me before: <boundaries>
Done means: <end state>

Each run, report: what you did, what you skipped and why, and anything
that looked different from previous runs.

4Handover checkBefore you widen a Bot's access or let it act unsupervised.

Summarise, in your own words:
1. What I have asked you to do.
2. What you are not allowed to do without asking me.
3. What you will do if <likely edge case> happens.

Do not start the task. I want to see whether the brief was clear before
anything runs.

Last checked against xAI’s own pages on 2026-08-20. Grok changes quickly; anything version-specific should be confirmed upstream before you rely on it.

Call plan from account signals

Build a discovery or deal-progression call plan from CRM history, account news and stakeholder notes, with a clear next-step decision.

Grok Bot basics6 min read

WorkflowIntermediate

Proposal draft from discovery evidence

Create a review-ready customer proposal from discovery notes, requirements and commercial points for sales teams.

Grok Bot basics6 min read

WorkflowIntermediate

Pipeline risks for manager review

A weekly pipeline review workflow for sales managers that produces a ranked risk list, evidence gaps and named follow-up actions.

Grok Bot basics7 min read

Found something out of date?

Grok changes quickly and this page is a snapshot. If something here is wrong, or you know a better resource, send it over.

Suggest a link →