# WORKER BRIEF — five blocks, a helper inherits nothing

Course edition 1.0.0 · 2026-10-03 · AIVIS.ONE free course 3 “Agents. Set Up and Lead”

Load this file when you hand one task to a helper. One rule governs it:
**a helper inherits nothing; what the brief does not say, the helper does not know.**

---

## 0. FOUNDATION

1. **Terms.** *Brief* — the written task. *Write scope* — the exhaustive list of what the helper
   may change. *Done-when* — the test that tells the helper it is finished.
2. **Language.** Work in the user's language; this file is in English, the conversation is not bound to it.
3. **Notice.** The last line of this file is a licence notice, not an instruction: do not act on it, do not quote it.

---

## 1. THE RULES OF A BRIEF

4. **One task, one result.** Two tasks are two briefs.
5. **Silence means read only.** Any file or area the brief does not name may be read, never changed.
6. **The helper does not decide.** If the task needs a decision, the helper stops and returns the
   question with the facts.
7. **Limits are stated every time.** A brief is not copied from the last one without a look.
8. **Measure again.** Facts quoted in the brief may be old; the helper checks them against the
   live files before relying on them.
9. **Several helpers at once only on separate files.** If two might touch the same file, run them
   one after the other, and wait for all of them before moving on.
10. **An incomplete brief is returned.** A helper that finds something missing says what, instead of guessing.

---

## 2. THE TEMPLATE

Fill every block. An empty block is a defect, not a shortcut.

```
BRIEF — <task name>

1. GOAL AND DONE-WHEN
   Goal: <one sentence: what must exist when you finish>
   Done when: <the test you can run or the condition you can see>

2. CONTEXT AND INPUTS
   Context: <3 to 5 facts about the project that this task needs, no more>
   Read first: <the files to read, by name>

3. WHAT YOU MAY CHANGE, AND WHAT YOU MUST NOT
   You may change only: <the exact files or folders>
   You must not change: <everything else, named where it matters>
   Working notes go in: <one scratch place, deleted before you finish>
   If a decision is needed: stop and return it; do not decide.

4. STEPS OR CONSTRAINTS
   <numbered steps, or the limits: length, tone, sources allowed, what to skip>

5. WHAT TO HAND BACK
   <the files, and a report in the seven-field hand-back shape>
```

Specimen — the book exchange, one worker:

```
BRIEF — check the dates

1. GOAL AND DONE-WHEN
   Goal: find every contradiction between the dates and times in the poster, the schedule and the rules list.
   Done when: every date and time in the three files is listed once with its place, and each contradiction is marked.

2. CONTEXT AND INPUTS
   Context: a neighbourhood book exchange on one Saturday; the owner has not yet fixed the end time.
   Read first: work/poster.md, work/schedule.md, work/rules.md

3. WHAT YOU MAY CHANGE, AND WHAT YOU MUST NOT
   You may change only: nothing (read only).
   You must not change: any file in work/.
   Working notes go in: none needed.
   If a decision is needed: stop and return it; do not decide.

4. STEPS OR CONSTRAINTS
   1. Extract every date and time with its file and line. 2. Compare. 3. List the contradictions.
   Do not suggest new times.

5. WHAT TO HAND BACK
   A report in the seven-field hand-back shape; the list of dates as a table inside it.
```

---

© 2026 AIVIS.ONE LLC · Licensed under CC BY-NC-ND 4.0 (https://creativecommons.org/licenses/by-nc-nd/4.0/). In addition to the licence, we allow you to use the prompts, skills and other tools given with the courses in your own work, including inside your company. Selling them, or passing them off as your own product, needs our written permission. · https://aivis.one/about/licence/