hermes

Rewrite an email bottom line first

Rewrites a long email or message bottom-line-first for a senior reader, with the ask and deadline up top and only the needed context, keeping every fact and listing what moved.

context

Most long work emails are written in the order the writer thought: background, history, analysis, and finally the ask in the last paragraph. Senior readers read in the opposite order of importance and often stop after two lines. Bottom line up front (BLUF) puts the ask or the conclusion, with its deadline, in the first sentence, then the two or three reasons that support it, then only the context the reader needs to act. The risk in rewriting is losing information: a figure, a caveat or a name dropped while cutting changes the meaning. So a good rewrite also accounts for every fact in the original.

task

Rewrite this email bottom line first.Only if [READER] is given: Reader: .Only if [ASK] is given: Ask: .

email

  1. Find the bottom line: the ask (decision, approval, input, action) with its deadline, or, if the email is informational, the single most important conclusion. If an ask was supplied and it conflicts with the draft (a different amount, date or option), do not choose silently: use [confirm: …] in the rewrite and explain under What changed. If neither the draft nor the ask reveals any point, ask what the reader should do or know and stop.
  2. Inventory the facts in the original: every figure, date, name, commitment, caveat, risk and attachment reference.
  3. Write the rewrite:
  • Subject line with a tag and the bottom line: "Decision needed by Fri: …", "Action: …", or "FYI: …".
  • First sentence: the bottom line, with the deadline and its reason if the original gives one.
  • Then up to three short bullets or sentences with the reasons or key facts that support it.
  • Then a short "Background" or "Details" part for the remaining context the reader needs to act or that the original included and must not be lost.
  • Close with the reply path ("Reply 'yes' to proceed").
  1. Keep the sender's relationship cues (greeting, thanks, a sensitive acknowledgement) but cut throat-clearing, repetition, hedging and narrative ("As you may recall…", "I just wanted to reach out…").
  2. Fit emphasis to the reader if given (cost, risk, time, customers) without changing any fact.
constraints
  • Keep every fact from the inventory unless it is pure filler; never add facts, figures or opinions that are not in the original or the ask.
  • Aim for no more than about 60% of the original's length, unless the original is already short. Facts beat length: if keeping every substantive fact makes the rewrite longer, keep the facts, move them into Background, and say so under What changed.
  • Plain words, active voice, figures as numerals.
  • Do not change the meaning, the commitments or the level of certainty (a "probably" stays a probably).
output format

Rewrite

Subject line, then the email.

Fact check

A table: fact from the original, where it is in the rewrite (first line, bullets, background), or "dropped: filler" with a reason. Nothing substantive may be dropped.

What changed

Two to four bullets: what moved to the top, what was cut, any conflicts or placeholders.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Writing and communication
category
Email
level
Beginner
made for
People manager, Project / program manager, Consultant / freelancer, Anyone, personal use
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-03
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install rewrite-email-bottom-line-first --target claude-code

This entry is in the full catalog, not the curated set the skills installer and plugins carry, so install it with the Hodios CLI.

pairs well with

All of Email
PromptEmail

Write a professional email

Drafts an email from rough intent with a specific subject line, the ask in the first two sentences and the right tone for the relationship, marking any detail it would otherwise have to invent.

write-professional-email
PromptEditing

Tighten prose

Tightens prose by cutting filler, redundancy and weak verbs toward a target reduction while keeping the author's voice, meaning and necessary qualifiers, and reports what it cut.

tighten-prose
PromptEmail

Request approval by email

Writes a bottom-line-first email asking a busy decision-maker to approve a budget, purchase, hire or exception, with options, cost, the risk of waiting and a one-line reply path.

request-approval-by-email
PromptEmail

Decline a request gracefully

Declines a request or invitation clearly and kindly in the first lines, gives an honest brief reason if wanted, offers only real alternatives and preserves the relationship.

decline-request-gracefully
PromptEmail

Reply to an email

Drafts a reply that answers every question and request in a received email from your stated position, matches its formality, proposes next steps and flags points you have not decided.

reply-to-email
PromptEmail

Triage an inbox

Sorts a batch of emails into reply, delegate, schedule and archive by your priorities, flags suspicious messages, and drafts the short replies and delegation notes.

triage-inbox