Anthropic extended Fable 5 access to July 12 — after that it leaves the Claude plan. These 3 prompts turn Fable's remaining days into things you keep: files, skills and plans that future models run off for months.
The first two prompts come from Every's Fable 5 prompt library — the audit prompt is our own.
Use this when: you want to find the use cases in your own context that justify a Fable run, before spending the time and tokens.
You are helping me decide which parts of my work are worth escalating to Claude Fable 5. Do not execute any of the work yet. Your job is to inspect my context, find strong candidates, and turn the best ones into ready-to-run Fable briefs.
My role and current goals:
[Describe your role, priorities, team, business goals, creative goals, or personal operating constraints.]
Use this context:
[List the sources you can inspect: repositories, project folders, docs, Notion, Slack, Linear/Jira, email, calendar, analytics, customer research, previous agent sessions, task lists, or anything else relevant.]
Constraints:
[List deadlines, privacy boundaries, accounts or tools you may not use, budget, sensitive areas, approval rules, and work that must remain human.]
First, inspect the available context. Do not brainstorm generic examples.
Build an inventory of:
1. Active projects.
2. Repeated workflows.
3. Stalled decisions.
4. Messy backlogs.
5. Work that spans several tools or sources.
6. Work where better planning, judgment, verification, or follow-through would materially improve the result.
Then identify the best candidates for Fable.
Score each candidate from 1 to 5 on:
1. Multi-source context.
2. Delegation fit.
3. Judgment required.
4. Clear finish line.
5. Leverage.
6. Fable fit.
Recommend Fable only when the task is large enough to justify a slower, more expensive run. Down-rank work that is short, obvious, highly interactive, hard to verify, or better handled by a faster Claude model or a human.
Return:
1. The top 10 Fable-worthy use cases, ranked.
2. The evidence you found for each one.
3. Why each one is or is not worth Fable specifically.
4. The expected deliverable.
5. The verification method.
6. The likely context, tools, and permissions needed.
7. Risks, blockers, or human decisions required.
8. A ready-to-run Fable Brief for the top three candidates.
For each ready-to-run Fable Brief, include:
- The problem to solve.
- The final outcome.
- Sources to inspect.
- Constraints.
- Suggested workflow.
- Human checkpoints.
- Evidence required before completion.
Stop after the ranked list and the three briefs. Do not start any Fable task until I choose one.
Why it works: a faster Claude model inspects your real projects and backlog, down-ranks work that belongs with a human or a lighter model, and hands back ready-to-run Fable briefs for the top three candidates.
Use this when: the task will take hours and can keep moving without your input.