Write a farewell message
Writes a goodbye message to colleagues, clients or a community when leaving a job or team, with specific thanks, handover pointers and a way to stay in touch, and nothing that burns bridges.
A farewell message is read by everyone, remembered by some, and occasionally forwarded. The good ones are short, thank people for specific things, make it obvious who to contact now, and leave a door open. The bad ones list every project ever touched, thank everyone generically, hint at grievances, or (with clients) announce where the person is going in a way that breaches their contract or looks like poaching. Specific thanks ("Leo, for the night you stayed until 2 a.m. to get the Lisbon launch out") mean far more than a list of names, but naming a few people in a company-wide email can make others feel left out, so the specific thanks belong in team messages or separate notes.
Write a farewell message for .
- If you cannot tell where the person is leaving from or roughly when, ask and stop.
- Shape the message by audience:
- team: personal; specific thanks to named people or moments from the leaving details; who takes over what; a way to stay in touch.
- company: shorter; thanks to groups and the organisation rather than a long list of names; what you are proud of in one line; contact details.
- clients: professional; thanks for the relationship; the date your involvement ends; the named successor and their contact; reassurance on continuity. Do not mention where you are going unless the leaving details say your employer has agreed.
- community: what the community gave you, a nod to what continues, how to find you.
- Include, in this order: the news and your last day; thanks with specifics from the leaving details; handover pointers (who to contact for what); how to stay in touch; a short warm close.
- Match the tone: warm is personal and sincere; brief is three to five sentences; funny uses one or two light touches drawn from the leaving details, never jokes at someone's expense.
- Write a subject line.
- Use only details from the leaving details. Never invent anecdotes, names, achievements or contact details; use
[your personal email],[successor name]and similar placeholders. - No grievances, criticism or hints about why you are leaving, even if the leaving details mention a hard exit. If the person was made redundant or is leaving on difficult terms, keep it gracious and neutral, and say so under Before sending.
- No confidential information about projects, clients or the reasons for leaving.
- Under about 200 words for team and community, about 150 for company and clients.
Message
Subject line, then the message.
Before sending
Bullets: placeholders to fill, timing (usually on the last day or the day before, after your manager and close colleagues know), whether to send individual thank-you notes to people not named, and for clients, whether your employer must approve the message first.
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
- level
- Beginner
- made for
- Anyone, personal use, Job seeker, People manager, Consultant / freelancer
- risk
- read-only
- version
- v1.0.1 · 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
use in
npx @hermes-hq/hodios install write-farewell-message --target claude-codenpx skills add hermes-hq/hodios-dist --skill write-farewell-message -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 handover document
Writes a handover for leave or a role change covering responsibilities, open work status, contacts, access, recurring tasks, known risks and first-week priorities, with gaps listed as questions.
write-handover-documentWrite a thank-you note
Writes a specific, heartfelt thank-you note that names what the person did, the detail that showed care and why it mattered, for cards, emails and post-interview notes.
write-thank-you-noteDecline 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-gracefullyReply 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-emailTriage 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-inboxWrite 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