hermes

Rewrite for clarity

Rewrites technical prose so the main point comes first and every sentence is plain and specific, while keeping every fact, number and caveat. Use on design notes, emails, RFC drafts and docs.

context

Technical writing is usually unclear for a few repeatable reasons: the conclusion is buried at the end, sentences hide the actor ("it was decided"), abstract nouns replace verbs ("perform an investigation of"), hedges pile up, and terms are used before they are defined. The fix is structural and line-level editing. Changing the meaning is not a fix: a clear sentence that says something the author did not mean is worse than the original.

task

Rewrite the text below for . Length: .

text

  1. Find the main point: the decision, request or finding the reader must take away. Put it in the first sentence or two.
  2. Order the rest by what the reader needs next: context and reasons after the point, details after the reasons.
  3. Edit line by line:
  • one idea per sentence; split sentences over about 25 words;
  • name the actor and use active verbs ("the cache drops stale entries", not "stale entries are dropped");
  • turn nominalisations back into verbs ("decide", not "make a decision");
  • replace vague words with the specific fact from the text ("in 3 of 40 runs", not "sometimes");
  • cut filler and stacked hedges, but keep a hedge that carries real uncertainty;
  • define or replace jargon the audience may not know; keep terms of art they do know;
  • use a list when items are parallel, and prose when they are connected by reasoning.
  1. Keep the author's voice and register. Do not make an informal note formal or the reverse.
constraints
  • Preserve every fact, number, name, code snippet, link, commitment and caveat. Do not add claims, examples or opinions that are not in the original.
  • If a sentence is ambiguous and the meaning matters, do not choose silently: pick the most likely reading and list the ambiguity under Check.
  • If the text is already clear, say so and make only the edits that help. Do not rewrite for the sake of it.
  • Code, commands and quoted error messages stay exactly as written.
output format

Rewrite

The rewritten text, ready to paste, in the original format (Markdown, plain text or email).

What changed

At most five bullets naming the main kinds of edits.

Check

Ambiguities you resolved and facts the author should confirm, or "None".

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
Software engineering
category
Developer writing
level
Beginner
made for
Software engineer, Tech lead / staff engineer, Technical writer
risk
read-only
version
v1.0.0 · experimental
reviewed
2026-10-02
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-for-clarity --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill rewrite-for-clarity -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the software-engineering plugin
claude plugin install hodios-software-engineering@hodios

The plugin brings every entry in this domain at once.

StyleOutput styles

Concise

Shortens answers by leading with the result and cutting preamble, recaps and filler, from light trimming to bare answers. Use when you want less reading and the same substance.

concise
PromptDeveloper writing

Write a conference talk proposal

Writes a CFP submission with title options, abstract, timed outline, takeaways and notes for reviewers, aimed at the event's audience and selection criteria. Use for engineers and developer advocates.

write-conference-talk-proposal
PromptDeveloper writing

Write a technical blog post

Turns engineering notes, code and results into a technical blog post with one clear takeaway, real numbers and working code, and no hype. Use for engineering blogs and write-ups of a project.

write-tech-blog-post
PromptDeveloper writing

Explain a technical issue to executives

Translates a technical issue or decision into a one-page executive brief with business impact, options, cost, risk and the specific ask. Use when leadership must decide or fund something technical.

explain-tech-to-executives
PromptDeveloper writing

Write an API deprecation notice

Writes the notice to API consumers for a deprecation or breaking change, covering what changes, the timeline, migration steps and where to get help. Use before announcing an API change.

write-api-deprecation-notice