Write a task brief MiOSbot can use

Name the deliverable

Start with what you want to receive: a comparison, a draft, a checklist, or a proposed change. “Draft a follow-up for this customer” is more actionable than “help with sales.”

Supply the context

Identify the project, audience, source material, and deadline. Point to the exact file or record when possible. Do not paste credentials into a task brief.

Set boundaries

Say whether the task is research-only, draft-only, or includes an authorized action. Specify what must remain unchanged and which account or environment is intended.

Define done

Ask for evidence that fits the task: source links for research, a file for a document, or test results for a code change. A configured setting is not the same as tested access.

Example brief

“Compare these three supplier proposals for our operations team. Use only the supplied files. Summarize scope, exclusions, and open questions in a table. Do not email vendors or accept an offer. Link each conclusion to its source.”