All Minds tutorials

How to brief your Mind: a practical job-brief template

Turn a loose request into a clear job for your Mind with a practical template covering the job, context, deliverable, quality bar and timing.

A Mind turning a clear brief into an actionable job

What is a Mind brief?

A Mind brief is a compact description of the work you want done. It records the assignment, relevant context, source material and expected deliverable in one place.

Think of it as the note you would send to a capable teammate before handing over a task. It should answer five questions:

  1. What is the job?
  2. What context and inputs matter?
  3. What should the deliverable contain?
  4. What does good look like?
  5. When do you need it?

Copy this Mind job-brief template

JOB Your job is to [specific task] so that [useful result].

CONTEXT AND INPUTS This is for [audience or decision]. Use these inputs: [files, links or data]. Keep in mind [existing decision, voice or priority].

DELIVERABLE Return [format and length]. Include [required sections, fields or links].

QUALITY BAR Prioritise [what matters most]. Use [source, tone or comparison standard].

TIMING Prepare it for [review date or deadline]. Cover information from [time period].

Copy the full version first. The sections below show how to fill each part without making the brief longer than the job requires.

Start with one job

The best opening line names the work.

"Help with marketing" leaves too much open. "Turn these meeting notes into a one-page campaign brief" gives the assignment a clear shape and a visible deliverable.

Try this sentence:

Your job is to [do the work] so that [useful result].

For example:

Your job is to review these interview notes and prepare a one-page summary so that I can compare the three customer needs before our planning meeting.

The sentence does not need to sound technical. It needs to make the finish line easy to recognise.

Add the context and inputs that change the work

Context explains what should shape the assignment. Inputs are the files, links, notes or data needed for the job.

Include the details that would materially affect the deliverable, such as the audience, purpose, source material, existing decision or house style. For a research brief, that may include the decision you are preparing to make and the sources you want considered. For a content task, it may include the intended reader, the approved tone of voice and an example of previous work.

A useful context block can be short:

This is for a marketing team deciding which topic to publish next. The reader is familiar with AI tools but does not write code. Use the attached source notes and search-gap report as the evidence base.

The goal is not to include every fact you know. Add the facts and inputs that affect the job.

Describe the deliverable

Name the format, length and level of detail you want.

Compare these two requests:

Research this topic.

Prepare a 600-word briefing with a direct answer, a comparison table and five linked sources. End with the three decisions I need to make.

The second brief defines an object you can recognise. It also keeps the assignment focused without turning it into a long technical specification.

Useful deliverables include a one-page brief, a prioritised table, an email draft, an agenda, a checklist or a set of options with a recommendation.

Set the quality bar

The quality bar explains what matters most in the deliverable. It can cover source quality, tone, level of detail or how choices should be explained.

For example:

Use first-party sources for product facts. Write in plain English. Separate confirmed facts from recommendations. Link every source beside the point it supports.

This is more useful than asking for something "high quality" or "professional". Those words sound positive but do not explain what you will look for.

If you already have an example that matches your expectations, include it and explain which parts are worth following.

State the timing

Finish the brief with the relevant time frame.

For a one-off job, name the deadline or meeting it supports. If the work supports a regular reporting window, name the review date and the period this brief should cover.

For example:

Prepare this for Monday's 10:00 HKT review. Use information published up to Friday at 18:00 HKT.

Clear timing helps when a brief depends on a reporting window, campaign date or editorial review.

Once all five parts are filled in, you have a complete brief you can read, edit and reuse for a similar future assignment.

Three example briefs for a Mind

Adapt the source material, timing and deliverable to your own work.

Research brief

Your job is to compare three personal AI agent products so that I can decide which ones deserve a closer trial. Use current official product pages and documentation. Return a 700-word brief with a comparison table, linked sources and three questions for further investigation. Write for a non-technical marketing reader. Prepare it for Friday at 16:00 HKT.

Meeting follow-up

Your job is to turn the attached meeting transcript into a follow-up pack. Return a short summary, a table of decisions and a list of actions with owner and due date. Preserve names and dates exactly as written. Prepare the pack before tomorrow's team check-in.

Content planning

Your job is to turn the attached search-gap report into five Minds-focused article ideas. For each idea, give the reader question, proposed title, Blog or Tutorial type, evidence needed and overlap with existing content. Use plain English and remove any topic that could apply unchanged to another AI brand.

How to sharpen a vague request

When a request feels too broad, improve the brief in this order:

  1. Replace the broad topic with one job.
  2. Name the reader or decision.
  3. Define the deliverable.
  4. Add the source material that should guide the work.
  5. State what matters most in the result.

"Plan my week" can become "Turn these 12 tasks into a Monday-to-Friday plan, grouped by deadline and estimated effort, with the three tasks I should start first." The improved version gives the work a shape.

Frequently asked questions

Do I need prompt-engineering experience to brief a Mind?

Start with normal language and describe the work as you would to a teammate. Name the job, relevant context and deliverable before adding technical detail.

How long should a Mind brief be?

Use the shortest brief that still explains the job. A small task may need three sentences. A research or planning assignment may need the full template plus source material.

Can I reuse the same brief?

Yes. Keep the stable parts, such as the audience, format and quality bar, then update the job, inputs and timing for a similar future assignment.

Should one brief contain several jobs?

Keep the main job singular. If the work has several parts, group them under one result and show the order in which they belong.

Where should I start if I have not chosen a Mind yet?

Read Five One-Click Minds and the first task to give each one, then use this template to brief the role that best matches your job.

Give your Mind a real job

Choose a Mind, copy the template and replace the brackets with your own work. The result is a complete brief you can understand at a glance and reuse for a similar future assignment.

Launch a Mind