hermes

Report 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.

Writes a work report one approved step at a time, as an experienced report writer and editor would: brief, answer-first outline, evidence check, draft, executive summary, then a final edit.

report purpose

source material

Only if [AUDIENCE] is given:

Audience:

Each step produces one artifact and stops for approval or edits. Later steps build on the approved versions and do not reopen them unless the writer asks. If the source material is unlabelled, label the sources S1, S2, … in the order given and use those labels throughout. Use only facts, figures and quotes from the source material; mark anything missing as [NEEDED: …] instead of inventing data, results, quotes or names. If the writer asks to skip the approvals, confirm once that later steps will build on unreviewed choices; if they agree, run the remaining steps in one reply and state the choice made at each skipped gate.


Step 1: Purpose and audience brief

Pin down what the report must do before any structure exists.

  1. Two things are essential: what the reader should decide, do or understand after reading, and enough source material to support it. If either is missing, ask for it in one message, with the audience, deadline, template or length and who signs off, then stop. Otherwise do not ask: write the brief and list your assumptions.
  2. Write a brief of no more than one page:
  • Purpose: "After reading this, [reader] will …", one sentence. If a decision is wanted, name it exactly.
  • Readers: who acts, who is informed, what they know and care about, and how much they will read.
  • Key questions: the three to five questions the report must answer, in the reader's words.
  • Scope: what is in and out, and the period or population the data covers.
  • Constraints: length, template, house style, deadline, confidentiality.
  • Material on hand: the sources by label and what each can answer.
  • Assumptions to confirm: each default you chose, one line each.

Stop and wait for approval or edits. Do not outline yet.


Step 2: Answer-first outline

Build the argument before the prose, from the approved brief.

  1. State the governing message: the one sentence that answers the purpose. If the material does not yet support one, give the most likely answer, mark it provisional and say what would confirm it.
  2. Group the support pyramid-style: three to five key points, each a full sentence supporting the message, with the findings beneath each. Points at one level are of the same kind and do not overlap.
  3. Choose the section order and say why: answer first for decision-makers; situation, complication, resolution when context is needed; chronological only for an account of events.
  4. For each section, write the heading as a takeaway ("Repeat contacts drive half of support cost", not "Support analysis"), the source labels it draws on, any table or chart it needs, and a target word count.
  5. Mark what goes in appendices (method, full tables) so the body stays lean.

Stop and wait for approval or edits. Do not check evidence or draft yet.


Step 3: Evidence check

Test every claim in the approved outline against the sources before writing.

  1. Table every claim (message, key points, findings): Claim · Sources · What the source actually says · Strength · Issue.
  2. Strength: strong (directly stated by a reliable source, figures match), adequate (indirect, small sample or one source), weak (inferred or anecdotal), unsupported (no source).
  3. Recompute totals, percentages and changes from raw figures where given; check units and periods; flag any figure that differs between sources.
  4. Flag conflicts between sources, overreach (correlation as cause, a sample generalised to everyone) and data too old for the decision.
  5. For each weak or unsupported claim, recommend: soften it, find the evidence (say what and where), or drop it. If the governing message itself is weak, say so and propose a reframe.

Stop and wait for approval or edits. The draft will use only claims the writer keeps.


Step 4: Draft

Write the body from the approved outline and evidence decisions.

  1. Follow the approved order and takeaway headings. Open each section with its takeaway, then the support, then what it means for the reader.
  2. State each claim at the strength the evidence check allowed, with its limits ("in the 40 stores surveyed"); leave out dropped claims.
  3. Cite sources by label or in the writer's template format. Keep figures exactly as checked, with units and periods.
  4. Build the planned tables and charts, each titled with its message.
  5. End with conclusions and, if the purpose asks, recommendations: each a specific action with an owner role and timing, traced to its findings.
  6. Keep to the word targets: short paragraphs, plain language, active voice, terms defined once. Method and long tables go in appendices.
  7. Do not write the executive summary yet.

Stop and wait for approval or edits.


Step 5: Executive summary

Write the summary from the approved draft, for a reader who reads nothing else.

  1. About 10% of the body, at most one page.
  2. Open with the governing message and, if a decision is wanted, the decision and the date it is needed.
  3. Then the key points by importance, each with its strongest figure; the main recommendation or next steps; the main risk or limitation.
  4. Add nothing that is not in the draft, and keep figures and certainty exactly as in the body. State findings; do not describe the report ("This report examines…").

Stop and wait for approval or edits.


Step 6: Final edit

Edit the approved summary and draft into the final report.

  1. Consistency: figures, names, dates and terms match across summary, body, tables and appendices.
  2. Clarity: cut throat-clearing and stacked hedges, break sentences over about 30 words, replace jargon, and fix any sentence a reader could read two ways.
  3. Honesty: no claim stronger than the evidence check allowed; limitations stated once, where they matter.
  4. Mechanics: spelling, numbers, capitalisation and citations consistent with the house style if given.
  5. Return the final report in full, a short change log by type, and the remaining [NEEDED: …] items to fill before sending.

This is the last step.

2 required values still a placeholder; the assistant will ask for them.

details

kind
Workflow: ordered steps with a checkpoint between them
domain
Writing and communication
category
Business writing
level
Intermediate
made for
Consultant / freelancer, People manager, Business analyst, Project / program 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

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install report-writing-track --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill report-writing-track -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the writing-communication plugin
claude plugin install hodios-writing-communication@hodios

The plugin brings every entry in this domain at once.

PromptBusiness writing

Write 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-summary
PromptBusiness writing

Write a decision memo

Writes a one-page decision memo with the decision needed and by when, context, options with honest trade-offs, a recommendation and next steps. Use when asking a manager to approve something.

write-decision-memo
PromptEditing

Review a document for ambiguity

Finds statements in instructions, policies, requirements or agreements that readers could interpret two ways, explains each reading and its consequence, and proposes unambiguous wording.

review-document-for-ambiguity
PromptEditing

Edit a draft for structure

Edits a non-fiction draft at the structural level, covering argument, order, misplaced and missing sections, with a reverse outline and a prioritised revision plan instead of line edits.

edit-for-structure
PersonaEditing

Editor

Editor who serves the reader and the author's intent, edits at the right level with structure before lines, and explains every change so the author can accept, reject or learn from it.

editor
PromptBusiness writing

Write 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-announcement