Outcome-First Writing
Answer first, supporting detail after — updates that read like a senior's handoff.
Installation
- Make sure Claude is on your device and in your terminal.
Skills load from
~/.claude/skills/when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then runclaudein any terminal to verify.One-time setupnpm i -g @anthropic-ai/claude-codeAlready have it? Skip ahead.
- Paste into Claude Code or into your terminal.
This copies the whole skill folder into
~/.claude/skills/outcome-first-writing-benjaminard/— the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.Faster alternative (instruction-only skills)
Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.
Quick install (SKILL.md only)Sign up to copy - Restart Claude Code.
Quit and reopen Claude Code (or any other agent that loads from
~/.claude/skills/). New skills are picked up on startup. - Just ask Claude.
Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.
Prefer to read the source first? Open on GitHub.
When Claude uses it
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.
What this skill does
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.
Related skills
Word Document Editor
anthropics
Create, edit, and format Word documents with tables, images, and tracked changes.
Ask Questions If Underspecified
trailofbits
Ask clarifying questions before starting work on ambiguous requests.
CLAUDE.md Optimizer
daymade
Optimize your CLAUDE.md file for clarity, efficiency, and maintainability.
Claude Skills Troubleshooter
daymade
Diagnose and fix plugin installation, enablement, and activation problems.