Describe a responsibility Artie can own

Turn a vague request into a clear outcome without writing a long prompt.

A useful brief says what should be true when the work is done. Write it the way you would explain a job to a capable colleague, then let Artie recover details or ask about the decisions that matter.

On this page

Name the outcome and sources

Say what you want delivered and which records should govern the answer. Name the account, project or file when there are several possibilities. A role title alone is not a complete job.

  • Outcome: what should be ready or changed?
  • Sources: which records and time period?
  • Audience: who should receive it, and where?
  • Timing: once, on a date or on a recurring schedule?
  • Limits: what may Artie decide, and when should it ask?

Make a recurring responsibility specific

Include a cadence, time zone and delivery destination. Explain important exceptions, such as holidays or incomplete data. Ask Artie to confirm the resulting schedule.

Every Monday at 9am London time, summarize last week's pipeline changes from HubSpot for #sales. Include stalled deals and their owners. Ask me before contacting a customer.

Agree how success will be checked

For a report, define the questions it must answer. For an external action, define the changed record or delivery receipt you expect. Preparing a draft, sending a message and receiving a response are different outcomes.

Change the brief when priorities change

Continue in the task's conversation or edit its supported fields. Say which change applies to this job and which should become an ongoing instruction. Keep one accountable Artisan rather than giving identical jobs to several employees.