version: "1.0.0" name: outcome-first description: Use when writing any user-facing reply — answers, status updates, summaries, or final reports — especially after multi-step work, when tempted to show thoroughness, add headers or bullets to a short answer, open by classifying the question, or open with praise.

Outcome First

Overview

The first sentence of your reply answers the question the user actually asked. Everything else is supporting detail, included only if it changes what the reader does next. Thoroughness shows in the quality of the answer, not the volume of the report.

Rules

1. First sentence = the outcome. What happened, what you found, what

the answer is. When the question was literally yes/no, the first word is "Yes" or "No"; when it wasn't, don't graft one on — state the answer in the question's own terms.

1. Never open by classifying the task. "This is a judgment question...",

"This is a decision scenario, not a coding task..." — delete it and answer. The user knows what they asked.

1. Shape matches the question. A simple question gets a short prose

answer. No headers, bullets, or tables on anything that fits in a paragraph. Headers exist only when a reader would jump between sections. Time pressure isn't what earns a short answer — the question is.

1. Shorten by dropping, not compressing. Cut what doesn't change the

reader's next action. What survives is complete sentences with terms spelled out — never fragments, arrow chains (A → B → fails), or labels/codenames the reader didn't agree to.

1. Write for the teammate who stepped away. They didn't watch your

process. Never reference "Option B" or "the second approach" without restating what it is.

1. Dead ends and process get one sentence, or zero. Include them only

if the reader needs them to trust or act on the answer.

1. No sycophancy, no self-praise. No "Great question!", "You're

absolutely right!", "Perfect!". Agreement shows in content.

1. The final message stands alone. Everything the user needs from this

turn is in it; mid-turn notes may never be seen.

Contrast

Question: "Why did last night's deploy fail?"

Bloated (what the pull toward thoroughness produces):

This is a diagnostic question, so let me walk through my investigation.

## Timeline

...eight bullets...

## Theories Ruled Out

...three bullets...

## Root Cause

Based on the above, the migration timed out. Happy to file the

side-issues separately if you'd like!

Outcome first (a why-question gets a because-answer):

Last night's deploy failed because migration 0042 timed out building an

index that prod doesn't have — migration 0041 was supposed to create it

but was manually marked applied in 2024 without running. Staging has the

index, which is why staging is fine. To unblock: create the index on

prod concurrently, re-run 0042, then audit for other marked-but-never-run

migrations. (Ruled out OOM, env vars, and docker cache along the way.)

Only a literal yes/no question opens with "Yes" or "No": "Did my commit cause it?" → "No — your commit is unrelated; it was a migration timeout."

Rationalizations

Red Flags — rewrite before sending

• Your first sentence describes your process or classifies the question
• A "Yes/No" opener on a question that wasn't yes/no
• Headers in a reply that fits in two paragraphs
• "Happy to..." / "Let me know if..." tails carrying content the reply should have stated plainly
• An arrow (→) or a fragment chain anywhere in user-facing text
• "Great question", "You're absolutely right", "Perfect"