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.
The most common failure in a reply is answering the first question and missing the rest, which costs another round trip. The second is committing to more than the sender intended: a polite reply that accidentally agrees to a date, a price or a deliverable. A good reply answers each point in the order that is easiest to read, says clearly what happens next and who does it, and mirrors the sender's formality without copying their mood if they are upset.
Draft a reply to this email:
My position:
- List every question, request, proposal and implied expectation in the email, numbered, including ones in postscripts and attachments mentioned.
- Map my position to each item. Where my position does not cover an item, do not guess an answer: put a
[your answer on …]placeholder in the reply and list it under Still to decide. - Match formality: mirror the sender's greeting, sign-off style, use of first names and length, adjusting up if they are senior or external. If the email is angry or upset, acknowledge the concern once, without matching the emotion, and move to substance.
- Order the reply for the reader: lead with the answer they most need (usually the main yes or no, or a decision); answer the remaining points briefly, numbered if there are more than three.
- Close with a concrete next step: who does what by when. Propose times or options when something needs scheduling.
- Keep the original subject line with "Re:" unless the topic has changed; if so, suggest a new subject.
- Do not commit me to anything beyond my position: no dates, prices, deliverables, apologies or admissions of fault I did not state.
- Do not invent facts about earlier conversations, attachments or third parties.
- Keep it as short as the points allow; no filler openings or closings.
- If my position conflicts with something the sender said is fixed (for example a deadline), keep my position and flag the conflict under Still to decide.
- If my position contains a point the sender did not raise (for example "no refund" when they have not asked for one), do not volunteer it in the reply unless it is needed to answer them; list it under Still to decide as "held back" so I can choose.
Points to answer
Numbered list of each point in their email, each marked "answered", "placeholder" or "declined".
Reply
Subject: Re: … The reply, ready to send apart from placeholders.
Still to decide
Bullets: each placeholder or conflict and the decision you need to make. "None" if complete.
2 required values still a placeholder; the assistant will ask for them.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- level
- Beginner
- made for
- Anyone, personal use, People manager, Customer support, Consultant / freelancer
- risk
- read-only
- version
- v1.1.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
use in
npx @hermes-hq/hodios install reply-to-email --target claude-codenpx skills add hermes-hq/hodios-dist --skill reply-to-email -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-writing-communication@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of EmailWrite 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-emailRewrite a text for tone
Rewrites a text in a target tone or register, such as warmer, firmer or more formal, without changing its facts, asks or commitments, and shows which tone dials moved.
rewrite-for-toneTriage 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-inboxDecline 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-gracefullyBuild a personal email template library
Builds a personal library of reusable email templates for the user's recurring situations, in their own voice from sent examples, with placeholders, subject lines and when-to-use notes.
build-email-templatesRequest 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