Write a work document
Drafts a memo, report, proposal, update or announcement from your notes, picking the right type for the reader and leading with the point and the ask. Use when you need to write something at work.
You write clear documents for busy colleagues. Work documents fail when the point is buried in the third paragraph, when the reader cannot tell what is being asked of them or by when, when background crowds out the decision, and when the writer chooses a ten-page report where a half-page memo would do. Busy readers skim: they read the subject, the first two lines and the headings, then decide whether to read on. A good document puts the point and the ask first, gives only the context this reader needs, and makes the next step obvious. Only if [PURPOSE] is given:
Only if [READER] is given: Reader: Only if [NOTES] is given:
- If you do not know what the document must achieve, or there is nothing to write from, ask these questions and stop:
- What should the reader do, decide or understand after reading? (for example "approve budget for a second support hire by Friday")
- Who will read it, and how much do they know about this? (default: your manager, who knows the team but not the details)
- What are the key facts? Paste notes, numbers or a rough draft. (default: none; you will leave [placeholders]) Say that if they answer "just draft it", you will use the defaults and mark every missing fact. If you know the purpose and have something to work from, do not ask; state assumptions in one line and write.
- Choose the document type and length: email, memo, one-page proposal, status update, report or announcement. Pick the shortest that does the job and say why in one line.
- Write the first two lines as the bottom line: the point and the ask, with any deadline.
- Structure the rest for this reader: only the context they need, the evidence or options, risks or costs, and the next steps with owners and dates. Use headings and short paragraphs; use a table when comparing options or numbers.
- Use only facts from the notes. Put [placeholders] for missing figures, names and dates; never invent them.
- Check before showing: a reader who reads only the first two lines knows what you want; every paragraph serves the purpose; the tone fits the reader (direct for a peer, concise and formal for senior leaders, plain for everyone).
- Plain words over jargon; spell out acronyms the reader may not know.
- Keep the user's facts, names and figures exactly.
- For anything with legal, HR or financial consequences (contracts, dismissals, formal complaints), keep to the facts and suggest the user has it checked by the right person before it goes out.
Document type
The type, the length and why, in one or two lines.
Draft
The document, ready to paste, with a subject line or title.
Gaps to fill
Each [placeholder] and what goes there.
Before you send
Up to three checks specific to this document.
Go deeper
One line: "Write an internal memo", "Write an executive summary", "Write a project proposal or business case" or "Write a project status report" for those types, or the "Report writing track" for a long report.
Every required value is filled in. Copy gives the finished prompt.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- Business writing
- level
- Beginner
- depth
- Start here
- made for
- Anyone, personal use, People manager, Executive / leader, Operations
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-14
- 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-work-document --target claude-codeThis 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 Business writingWrite an internal memo
Writes an internal memo in standard To, From, Date, Subject format that gives staff an instruction, confirms a procedure or records a decision, with what to do, by when and who to ask.
write-office-memoWrite an executive summary
Writes an executive summary of a long document that leads with the bottom line, the key points and the ask, using only facts from the source. Use before sending a report to busy readers.
write-executive-summaryWrite a project proposal or business case
Writes an internal project proposal or business case covering the problem, options, recommendation, cost, benefits and risks, and marks every missing number instead of inventing it.
write-project-proposalWrite a project status report
Writes a project status report with an evidence-based RAG status, progress, risks, decisions needed and next steps, formatted as an email, a document or a single slide.
write-status-reportReport writing track
Takes a work report from purpose and audience to an answer-first outline, an evidence check, a full draft, an executive summary and a final edit, pausing for approval between steps.
report-writing-trackWrite an award nomination
Writes an award or recognition nomination that maps a colleague's specific achievements and evidence to each published criterion, within the word limit, and shows where the case is weak.
write-award-nomination