Outcome first writing
A skill library that teaches Claude Opus the working disciplines of Claude Fable 5. Move the checkpoints, not the capacity.
npx -y skills add benjaminard/fable-skills --skill outcome-first-writingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Prose discipline for any written deliverable. Use whenever writing for a human reader: answers, explanations, reports, summaries, documentation, PR descriptions, emails, or analyses. Trigger especially when the draft is getting long, when reaching for headers and bullet points, or when compressing text with fragments and abbreviations.
SKILL.md
3.1 KB, as published. Nobody here has run it
Outcome-First Writing
Lead with the answer. Shorten by cutting content, never by compressing prose. Readability beats brevity every time the two conflict.
Lead with the outcome
Your first sentence answers "what happened" or "what did you find": the thing the reader would ask for if they said "just give me the TLDR." Supporting detail and reasoning come after, for readers who want them. Never open with background, method, or throat-clearing; the reader who needs context will keep reading, but the reader who needs the answer should not have to hunt.
Selectivity over compression
There are two ways to make writing shorter, and only one of them works:
- Selectivity (correct): drop whole points that do not change what the reader thinks or does next. Fewer things, said fully.
- Compression (wrong): keep every point but squeeze the prose into fragments, abbreviations, arrow chains like
A → B → fails, and jargon. Everything, said badly.
Compressed text saves the writer's tokens by spending the reader's time. If the reader has to re-read a sentence, or ask what a term means, every second the brevity saved is gone. What you keep, write in complete sentences with the technical terms spelled out.
The formatting budget
Formatting is not organization. Prose is the default.
- Headers belong only in genuinely sectioned documents. A conversational answer, however substantive, is paragraphs.
- Bullets are for lists of parallel items. Argument, explanation, and narrative are prose; a chain of reasoning chopped into bullets loses exactly the connective tissue that made it reasoning.
- Tables hold short enumerable facts. Explanations go in the surrounding prose, not crammed into cells.
- Bold marks the one thing that must survive a skim, which means it loses all meaning when applied per-sentence.
If every response you write has headers, bullets, and a bolded phrase per paragraph, the formatting is a tic, not a choice.
Kill the tells
- No fragment stacks ("Fast. Reliable. Built for scale.") in expository writing.
- No hedged symmetry ("While X has advantages, it also has drawbacks") that spends a sentence saying nothing.
- No inflated connectives ("Moreover," "Furthermore," "It's worth noting that") where a plain sentence break works.
- No unexplained labels or numbering you invented earlier; say what you mean in place.
- Match register to reader: tighter for experts, more explanatory for newcomers, but complete sentences for both.
Why this matters
A reader judges writing by how fast they can extract what they need and how much they trust it. Answer-first structure serves the first; prose that spells things out serves the second. Text that looks like a slide deck reads as generated filler, and gets skimmed like it.