Five Things Every Assignment Needs
Object, result, format, safety bounds, and how you will accept it. Miss one, and even the right direction is unusable.
“Handle this for me” is not an assignment. It hands the other side the right to guess: which file, what done looks like, where the line is, how you will accept it. When the direction is right and the artifact is still unusable, you usually skipped one of the five things below. The model was not the bottleneck.
After reading, you should be able to answer:
- What five things does an assignment need at minimum?
- What kind of failure shows up when you skip each one?
- Why keep the skeleton separate from a product-specific example?
Each of the five owns a slice
- Object: which material, and where it is now. No object, and it invents something that looks right.
- Action and result: what to do, and what to hand back. The result has to be an artifact, not “summarize this.”
- Format and rules: structure, units, names. If you do not say, it will pick whatever feels tidy.
- Safety bounds: do not overwrite the original, do not send, do not pay, stop when unsure. Bounds are stop conditions, not manners.
- How you will accept it: numbers must recompute from the detail rows, tests must pass, a missing column means it is not done. Without this, you can only take delivery by vibe.
Codex starts from a goal. Grok Bot hire cards spell duty, sources, a judgment bar, and a report format. Same skeleton, different product names.codex-overview xai-bot
Skip one, fail differently
| Missing | What you usually get |
|---|---|
| Object | Invented material, or the wrong file |
| Result | A paragraph you still have to land yourself |
| Format | Readable, not usable; editing is slower than redo |
| Bounds | Overwritten originals, outbound mail, spent money |
| Acceptance | Both sides think it is done until you check |
“Right direction, unusable output” is almost always missing format or missing acceptance. That is not a prose problem. You did not give it a check.
Skeleton first, product example second
These five are the skeleton. You should be able to retell them after you switch products. Where to click in one app does not belong in the skeleton. When you need an example, name the product and treat it as a sample, not a universal truth. Next, draw the line: what to hand off, what to keep. When you actually run a job, use the five-step loop.