Write a briefing note
Writes a public-sector style briefing note for a minister, director or board with purpose, background, considerations, options and a recommendation under the required headings.
A briefing note lets a senior decision-maker, often reading between meetings, understand an issue and act on it in a few minutes. Government departments in Canada, the UK, Australia and elsewhere use similar shapes: a purpose line saying whether it is for decision or information, a short summary, background, the current status, considerations (financial, legal, policy, stakeholder, communications, equity, risk), options with honest pros and cons, a recommendation, and next steps. Public servants write them impartially: the facts and risks are set out even when they are unwelcome, the recommendation follows from the analysis, and nothing is shaped for party-political advantage. Notes fail when the ask is buried, when options are straw men, when the legal or financial risk is missing, when acronyms go unexplained, or when they run past the page limit and are not read.
Write a briefing note for , no longer than pages (about 450 words per page).
Only if [OPTIONS] is given:
Only if [REQUIRED_HEADINGS] is given: Required headings, in this order:
- If you cannot tell what the issue is or the background has no facts to analyse, ask up to three questions and stop.
- Decide the type: for decision (a recommendation and a decision line are needed), for information, or for a meeting (add key messages and likely questions). Use the type the issue states; otherwise infer it and say so under Gaps and checks.
- Use the required headings exactly and in order if given. Otherwise use: Purpose; Summary; Background; Current status; Considerations; Options; Recommendation; Next steps. Drop Options and Recommendation for an information note.
- Write each part:
- Purpose: one sentence: "To seek your decision on…" or "To inform you of…", with the date a decision is needed and why.
- Summary: three to five bullets a reader could stop after.
- Background and Current status: only the facts needed to understand the options, with figures and dates from the input, in numbered paragraphs.
- Considerations: the financial, legal, policy, stakeholder, communications and equity points that apply, each in a sentence or two. Name who has been consulted and who has not.
- Options: two to four genuine options including the status quo if realistic, each with benefits, risks, cost and timing on the same basis. Do not weaken alternatives to favour the recommendation.
- Recommendation: the option and the deciding reason, and its main risk with mitigation.
- Next steps: what happens after the decision, by whom and when.
- For a decision note, end with a decision line: "Agreed / Not agreed / Discuss", with space for signature and date.
- Spell out every acronym on first use. Use plain, neutral language.
- Stay within pages; if the material cannot fit, keep the analysis and suggest an annex for detail under Gaps and checks.
- Use only the facts in the input. Never invent figures, legal positions, stakeholder views or consultation that did not happen; mark gaps
[NEEDED: …]. - Impartial: no party-political framing, no spin, no omission of a material risk even if the reader will not like it. If the input asks to leave out a material risk or to frame the note for political advantage, keep the risk and note why under Gaps and checks.
- No hedging chains; state uncertainty once, with what would resolve it.
Briefing note
Header lines (To / From / Date / Subject / Type: for decision, information or meeting), then the note under its headings with numbered paragraphs.
Gaps and checks
Bullets: [NEEDED: …] items with where to get them, assumptions made, who should clear the note (legal, finance, communications) before it goes up.
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
- People manager, Consultant / freelancer, Business analyst, Executive / leader
- 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-briefing-note --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 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-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 public consultation response
Writes a response to a government or regulator public consultation that answers the published questions in order, states the respondent's position with evidence and proposes concrete changes.
write-public-consultation-responseWrite a policy brief
Turns research findings into a policy brief for decision-makers with the problem, the evidence and its strength, costed options and recommendations. For researchers and think tanks.
write-policy-briefWrite 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-proposal