Write a Grok Bot task brief that produces useful work

Copy the template

Outcome: Complete [one specific business result].
Sources: Use only [named systems, folders, pages or records].
Constraints: Follow [rules, exclusions, limits, tone and freshness window].
Deliverable: Produce [exact format] in [location], including [required fields and evidence].
Review point: Stop before [send, publish, pay, delete, change access or commit]. Present [what the reviewer needs to decide].

Example: overdue invoice queue

Outcome: Prepare this week's overdue-invoice follow-up queue.
Sources: Use the QuickBooks aged receivables report dated today and the approved customer-notes sheet.
Constraints: Include only invoices more than seven days late, exclude disputed accounts and use the approved reminder tone.
Deliverable: Create one review row per invoice with customer, amount, due date, last contact, source link and reply draft.
Review point: Do not send anything. Flag disputed, VIP or missing-context accounts for the finance owner.

Add evidence and failure rules

Require a source link or file path, source timestamp and Could not verify section. Tell the Bot what to do when information is missing, stale or conflicting. A useful brief defines how to stop, not only how to succeed.

Turn it into a reusable workflow

Run the task with one normal case and at least two failures. When the output is consistently reviewable, use the skill template to preserve the process. Schedule it only after that skill works.