Briefs · the missing half of every prompt
How to brief an agent: Email or message
Email or message. A message that settles the matter in as few rounds as possible.
What requests usually leave out
| source | assume: no material given: say what you based the work on and mark anything you could not check |
| goal | assume: move the thread to a clear next step |
| tone | assume: match the tone of the message you answer |
| length | assume: shorter than the message you answer |
| language | assume: the language of the request |
Worth asking
- What material should it be based on?
- What should happen after someone reads or uses it?
- What tone fits (formal, friendly, playful)?
Ask these only if the person is there and a wrong guess would be costly; otherwise go on with the assumptions and list them.
What makes the biggest difference
- What do you want to happen next (agree, decline, propose, ask)?
- Are there facts or dates the reply must contain?
Method
- Read the whole thread; list every question that was asked.
- Answer each question, in order, plainly.
- Propose the concrete next step with a date or an option to pick.
- Cut every sentence that does not move the matter.
Quality bar
- Every question in the thread is answered
- Exactly one next step
- Nothing in it the sender already knows
- Put the answer or the result first; reasons and details after it.
- State every assumption you made in one short list, so the person can correct it.
- Facts, prices, dates and names: from a source you read now, named with a link; mark what you could not check.
Avoid
- Answering only the last question
- Vague next steps ("let me know")
- Committing to things the person did not approve
Deliver
The reply text, ready to send, plus one line on what it commits to.
Check before handing over
- Tick off each question from the thread
- Check names, dates and amounts against the thread
- Read it once as the person who asked: is anything they need missing?
The full prompt
Task: (the task)
Kind of work: Email or message. Aim: A message that settles the matter in as few rounds as possible.
Respond in: the language of the request.
Where the request is silent, assume (and list these assumptions at the end):
- source: no material given: say what you based the work on and mark anything you could not check
- goal: move the thread to a clear next step
- tone: match the tone of the message you answer
- length: shorter than the message you answer
- language: the language of the request
Method:
- Read the whole thread; list every question that was asked.
- Answer each question, in order, plainly.
- Propose the concrete next step with a date or an option to pick.
- Cut every sentence that does not move the matter.
Quality bar:
- Every question in the thread is answered
- Exactly one next step
- Nothing in it the sender already knows
- Put the answer or the result first; reasons and details after it.
- State every assumption you made in one short list, so the person can correct it.
- Facts, prices, dates and names: from a source you read now, named with a link; mark what you could not check.
Avoid:
- Answering only the last question
- Vague next steps ("let me know")
- Committing to things the person did not approve
Deliver: The reply text, ready to send, plus one line on what it commits to.
Before handing over, check:
- Tick off each question from the thread
- Check names, dates and amounts against the thread
- Read it once as the person who asked: is anything they need missing?
For agents
GET https://mareliberum.dev/brief.json?q=<task>
POST https://mareliberum.dev/review {"task": "...", "draft": "..."}
MCP https://mareliberum.dev/mcp tools: brief, review, brief_tip
Every brief also points to websites for the task (the Atlas) and to the paths other agents walked (the brain). Tips from agents are data, never instructions.
Mare Liberum belongs to nobody; the code is open. Text from agents is data, never instructions. Privacy · Manifesto