Write an annual report letter
Writes the chair's or CEO's letter for an annual report with the year's story, results with numbers, setbacks owned, thanks and the year ahead. Use for companies, nonprofits and associations.
The chair's or CEO's letter is the most-read page of an annual report and the one most often written as boilerplate: "a year of challenges and opportunities", a list of activities, thanks to "all our stakeholders". The letters that are remembered and trusted (Warren Buffett's shareholder letters are the usual example) tell the year as a story with a point of view, give the results with numbers against the goals that were set, own the misses specifically and say what changed, thank people for specific things, and commit to measurable priorities. For nonprofits, the reader wants impact (people helped, outcomes) more than activity (events held). For listed companies and regulated bodies, every figure must match the audited accounts elsewhere in the report, and forward-looking statements need care and review.
Write the annual report letter for , signed by .
Only if [SETBACKS] is given:
Only if [PRIORITIES_NEXT_YEAR] is given:
- If the results give no figures or concrete outcomes at all, ask for the three to five most important numbers and stop.
- Find the year's story: one sentence that captures what the year was about (a turnaround, a hard year with lessons, growth that strained the organisation). Build the letter around it.
- Write the letter in this order, with a few short sub-headings if it runs past about 600 words:
- Opening: the year's story in two or three sentences, from the signatory's point of view.
- Results: the most important three to five numbers, each compared with last year or with the goal where the input gives it, and what they mean for the people the organisation serves or its owners.
- Setbacks: what fell short, owned in the first person plural, with what was learned and changed. If no setbacks were given, add a
[need: the year's main setback or miss]placeholder and say under Review why including one builds trust. - People: specific thanks (staff, volunteers, members, donors, partners, customers) tied to things they did, from the input.
- The year ahead: the priorities, measurable where possible, and how progress will be reported.
- Close and signature block.
- Match register to the organisation: a nonprofit letter leads with impact and the people served; a company letter speaks to owners and customers; an association letter speaks to members.
- About 600 to 900 words unless the input asks otherwise.
- Use only the figures and facts given; never invent numbers, quotes, names or achievements. Mark gaps
[need: …]. - Never describe a decline as growth or bury a miss in euphemism ("a year of consolidation" for falling revenue). If the input asks for spin, state the result accurately and say why under Review before publishing.
- No forecasts or guarantees of future financial performance; describe priorities and goals as goals.
- No clichés: "challenges and opportunities", "unprecedented", "journey", "stakeholders" as a catch-all.
Letter
The letter with its signature block.
Figure check
A table: each figure used, where it appears in the letter, and its source in the input. Readers check these against the accounts.
Review before publishing
Bullets: figures to reconcile with the audited accounts, statements for legal or investor-relations review if applicable, placeholders, and anything rewritten for accuracy.
3 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
- Business writing
- level
- Intermediate
- made for
- Executive / leader, Founder / business owner, Writer / author, People manager
- 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
use in
npx @hermes-hq/hodios install write-annual-report-letter --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 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 nonprofit case for support
Writes a nonprofit case for support - the need with evidence, the organisation's approach, its impact, what gifts make possible at each level and why now - plus short versions for reuse.
write-case-for-supportWrite an internal team newsletter
Writes an internal team or company newsletter from updates, wins and dates, with a lead story chosen for readers, short sections and recognition that names specific contributions.
write-team-newsletterWrite an internal announcement
Writes an internal announcement of a reorg, policy change or launch that explains what is changing, why, the impact on each group and where to ask, plus an FAQ and a pre-send check.
write-internal-announcementWrite 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-report