How to Give Work to AI: A Beginner Task Brief

Codex Beginner Path · Step 3 of 5

• Previous: Choose a safe workspace
• Goal: turn one job into a brief that AI can understand and you can review.
• Estimated time: 8 minutes.

💡 Do not say only “handle this.” Explain what to do, what information may be used, what must not happen, and what must be delivered.

1. Why One Sentence Fails

“Organize this,” “analyze these files,” and “handle the folder” leave the goal, scope, allowed operations, output format, uncertainty rules, and completion standard undefined. The more ambiguous the brief, the more the AI must guess.

2. The Six-Part Brief

2.1 Goal

State why the work matters: Organize product material by model so sales staff can find it quickly.

2.2 Scope

State exactly what may be used: 01-originals is for human comparison only. Process only files in 02-to-process, which is the sole AI input for this task. Do not read or modify other folders.

2.3 Steps

Use an explicit sequence:

1. Inventory the files first.
2. Identify the likely product models.
3. Propose an organization plan.
4. Process at most 3 files whose classification can be confirmed.
5. If fewer than 3 files can be confirmed, process the actual confirmable number. Do not invent files or expand the scope.
6. Wait for my confirmation before continuing.

2.4 Forbidden Actions

For a first task: no deletion, overwriting, external sending, upload, or publication. If an output already exists, skip it and report the conflict instead of replacing it.

2.5 Deliverables

Name the outputs: an organized folder, a product-material index, and a processing log.

2.6 Uncertainty

Put uncertain items in 04-needs-review. Never invent product specifications from filenames.

3. Copyable Template

Please help me complete [task name].

1. Goal
I want this work to achieve: [purpose and expected result].

2. Information scope
Use only: [folder, files, or other allowed material].
Do not read or process anything outside this scope.

3. Steps
- inventory the existing material;
- restate your understanding and proposed plan;
- complete a sample of at most 3 confirmable files;
- if fewer than 3 can be confirmed, use the actual number without inventing files or expanding the scope;
- wait for confirmation before processing the rest.

4. Forbidden actions
- do not delete source files;
- do not overwrite source files or existing outputs; skip and report an existing output instead;
- do not send, upload, or publish;
- do not present an inference as a confirmed fact.

5. Deliverables
Deliver: [document, spreadsheet, folder, checklist, or report].
Also list every file created, copied, moved, renamed, or modified.

6. Uncertainty
Mark uncertain items as “needs review” and stop instead of guessing.

Before acting, restate:
- the goal;
- the material you will use;
- the actions you will not take;
- the deliverables.

Wait for my confirmation before execution.

4. Ask AI to Restate the Task

A restatement exposes misunderstandings before files change. If “organize by product model” becomes “organize by image color,” correct it before execution.

How Can a Beginner Tell That the AI Really Paused?

Confirm all four points instead of accepting a vague “understood”:

• it explicitly says that it is waiting for your confirmation;
• it has not started commands or reported created, changed, moved, or copied files;
• it restates only the goal, allowed material, red lines, deliverables, and uncertainty handling;
• if the restatement is wrong, correct the rule before sending “start,” “execute,” or “continue.”

Screenshot boundary

The screenshot uses fictional teaching material in an already-installed Windows 11 environment with CC Switch and the third-party Laifa AI configuration. It is a reference test of the “restate first, then wait for confirmation” interaction pattern. It does not verify OpenAI's official ChatGPT sign-in, and its older visible folder wording should not be treated as proof that the revised 02-to-process-only boundary was tested.

5. Start with a Small Sample

Process at most 3 confirmable files
→ if fewer than 3 are confirmable, use the actual number
→ review classification and format
→ correct the rule
→ continue only after approval

“At most 3” is a ceiling, not a quota. If only one or two files can be confirmed, process only those files. Never read outside 02-to-process, invent another file, expand the task, or overwrite an existing output just to reach three.

A sample tests understanding, output format, classification rules, missing fields, and compliance with red lines at low cost.

6. Use Three Evidence States

State	Required handling
Confirmed	Process according to the rule
Plausible but unsupported	Label as an inference and request confirmation
Cannot determine	Move to needs review and do not guess

This is especially important for product specifications, certifications, prices, lead times, and customer information.

7. Completion Check

• The goal and allowed material are explicit.
• The task starts with inventory and restatement.
• A sample of at most 3 confirmable files comes before bulk processing; fewer files are handled at their actual count.
• Deletion, overwrite, upload, sending, and publication are forbidden.
• Deliverables and the change log are named.
• Uncertain facts have a clear handling rule.

8. Next Step

👉 Continue to Step 4: organize a small set of product materials →

← Return to Step 2: choose a safe workspace