15 Fable prompts for people who don't code

Fable 5 left the Claude subscription plans on July 7. After that it’s metered: $10 per million input tokens, $50 per million output.

So every video and thread that week was some version of “run these coding jobs before the deadline.” Big refactors. Test suites. Migrations.

Great advice, for the people it’s for. But most people don’t have a codebase. They have a business, a calendar, an inbox, and a family schedule that eats 30 minutes a day nobody can account for.

The coding crowd figured out something first: Fable’s edge was never typing speed. You’re renting judgment. And judgment works on anything you can paste into a chat.

I spent the last year as the non-technical one learning this the hard way. My prompts used to be polite little work orders. “Summarize this.” “Review that.” The output was fine. Fine is the problem. An assistant with no stake gives you assistant answers.

The fix isn’t a better-worded task. It’s a stance. Give the model an identity with something to lose, a goal instead of a checklist, and permission to be blunt. That’s also exactly how Anthropic says to prompt Fable: brief goals over step-by-step instructions, because over-specifying degrades it.

So here are 15 stance prompts for the rest of us. Every one is copy-paste. Every one runs on things you already have: your statements, your calendar export, your notes, your landing page.

The business ones

1. The eulogy

Morbid? Yes. But post-mortems written in advance are the cheapest consulting on earth.

2. The acquirer

Nobody inside a company can answer “what would a rival delete.” The model has no feelings about your sunk costs.

3. The churn confession

Compare its answer to what you assumed was wrong. The gap between the two is usually the whole insight.

4. The refund letter

This one finds the gap between what you sell and what you ship, fast.

5. The pricing bully

6. The mystery shopper

The money ones

7. The CFO who hates me

8. The calendar audit

The personal ones

9. The pattern reader

Fair warning: this one is not fine. Run it anyway.

10. The inbox archaeologist

11. The household COO

We run a version of this at home with an agent named Juno. The 30 minutes exists. It’s usually somewhere between school pickup logistics and “what’s for dinner.”

12. The negotiation postmortem

Roleplaying the next negotiation is a parlor trick. Grading the last three from the actual transcript is how the pattern breaks.

The meta ones

13. The last-mile detector

I have 350+ pieces of content drafted and about 10 published, so this prompt was built from personal shame. It works.

14. The agent audit

Instructions written for older models actively drag Fable down. Shorter is smarter now.

15. The honest investor update

You don’t have to send it. You do have to read it.

How to run these

Give it real material. Stances need stakes, and stakes need data. Paste the statements, attach the export, point it at the folder. Vague inputs get you horoscopes.

Set effort to high. Anthropic recommends high as the default and xhigh for the heavy stuff. These audits are the heavy stuff.

Don’t ask it to explain its reasoning. That can trigger a refusal, and in some setups Fable quietly hands your task to Opus 4.8 and burns your usage doing it. Ask for conclusions and evidence instead.

Mind the meter. These prompts chew through tokens reading your material. That’s exactly what gets expensive at metered rates, so batch them and bring your best inputs.

And if you do have a codebase: I wrote 10 more in the same style that treat it like a company. The day-one CTO, the activist investor, the departing cofounder.

The models got smart enough to tell you the truth. Most people are still asking them to summarize things.

I write about running a business (and a household) with AI agents, the wins and the faceplants. The newsletter is here.