Working with Fable 5: delegation is the new prompting.
For two years the skill was writing a clever prompt and getting a clever answer back. Fable 5 changes the game: it can work on its own for hours, across many steps. The people who get the most from it stop writing prompts and start writing briefs — the way you'd hand a project to a capable new hire.
The mental model
Stop asking. Start delegating.
A prompt is a question: "Write me an email about X." A brief is an assignment: the goal, the constraints, what done looks like, and what to do when something's unclear. Earlier models needed prompts because they did one thing then stopped. Fable 5 can carry a whole task — so the quality of your brief now matters more than the cleverness of your wording.
With older models you steered every turn. With Fable 5 you set the destination well, then check the work — like managing a sharp employee instead of operating a tool. Vague brief, wandering result. Tight brief, finished work.
Pattern 01 Lead with the goal, not the steps
Say what "done" looks like before you say how
Weaker models needed you to spell out each step. Fable 5 plans the steps itself — if you tell it the actual outcome you want. Define success first; let it figure out the route.
Instead of a step list, write a brief
Why it works
- The model owns the planning, which is what it's now good at
- "Done looks like" prevents the 80%-finished result that needs three more rounds
- The "say so rather than guessing" line is your hallucination guardrail
Pattern 02 Set constraints up front
The guardrails that keep a long task on the rails
When a model works for a while on its own, small wrong assumptions compound. Constraints are how you prevent drift before it starts — the same things you'd tell a contractor before they begin, not after.
The constraints worth stating every time
Why it works
- "Stop and ask before assuming" turns a runaway task into a checkpoint
- The "must not include" line is the single most valuable instruction for trustworthy output
- Constraints stated once at the start beat corrections made five steps in
Pattern 03 Build in checkpoints
Catch a wrong turn at minute 5, not hour 2
The failure mode with autonomous work is discovering at the end that it went the wrong direction early. The fix is to ask for a plan first, approve it, then let it run — exactly how you'd manage a big assignment from a person.
The two-stage handoff
Why it works
- You correct a misunderstanding in 30 seconds instead of redoing an hour of output
- The model's stated assumptions often surface a gap in your brief
- For genuinely long tasks, add: "check in with me at the halfway point before continuing"
Pattern 04 Make it check its own work
The single instruction that raises quality the most
One of Fable 5's genuinely new strengths is reflecting on and validating its own output — Anthropic specifically calls this out at high effort. You unlock it by asking for it explicitly.
The self-review close
Why it works
- The model catches its own thin spots before you have to
- The "note on what you changed" tells you where to apply your own judgment
- It mirrors how good professionals work: draft, critique, revise
Final challenge: write one real brief
Take a task you'd normally hand Claude as a quick prompt — and instead write it as a full brief: goal, constraints, a checkpoint, and a self-review close. Run it on Fable 5. Notice how much less back-and-forth it takes to reach something you'd actually use. That gap is the skill this whole release rewards.
What you can do now
- Tell the difference between a prompt (a question) and a brief (an assignment)
- Lead with the goal and "done looks like," and let Fable 5 plan the steps
- Set constraints up front to keep a long task from drifting
- Use a plan-first checkpoint to catch wrong turns early
- Add a self-review close to raise output quality
- Stay the editor of record on anything that leaves your hands