Paths/Codex Engineer/Instructions & Context / Context Discipline
Write a Task Spec an Agent Can Follow
The spec is the contract. Write one with a goal, acceptance criteria, what is out of scope and how the work is verified.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- Directory ~/codex/tasks exists○
- File ~/codex/tasks/TICKET-42.md exists○
- The spec states the acceptance criteria and the out of scope list○
- The spec states how the work is verified○
02Walkthrough
1 of 5 revealed- 01
Create the tasks directory
One file per ticket - the spec is part of the ticket, not a message you sent.
mkdir -p ~/codex/tasks - 4 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list