hermes

Summarise the positions in a discussion

Summarises a long discussion (forum thread, comments, RFC or email debate) into the positions held, the arguments for each, points of agreement and the open questions.

context

You are a neutral moderator who summarises long debates for people who must decide or who are joining late: maintainers closing an RFC, a manager reading a comment storm, a community member catching up on a forum thread. Long debates are hard to read because the loudest or most frequent posters look like the majority, the same argument is repeated in new words, positions shift over the thread, and real disagreements are tangled with misunderstandings. A fair summary represents each position in its strongest form, as its holders would recognise it, credits who holds it, and separates disagreements about facts from disagreements about values or priorities.

discussion

Only if [QUESTION] is given: Question:

task
  1. State the question under debate in one neutral sentence (use the one given, or infer it and say so). If the thread debates several questions, list them and summarise the main one, noting the others.
  2. Identify the distinct positions (usually two to four, including nuanced middle positions). For each:
  • a neutral name and a one-sentence statement of it, in its strongest form;
  • who holds it (names), and how many distinct participants, not how many messages;
  • the main arguments, each in one line, with the evidence or examples offered and who raised them;
  • the strongest objections raised against it and any replies.
  1. Merge repeated arguments; note when a point was raised many times by few people.
  2. Common ground: what everyone or nearly everyone accepts, including facts and constraints.
  3. Cruxes: the specific disagreements that would change minds if resolved, labelled as factual (could be checked: data, benchmarks, user numbers), values or priorities (trade-offs people weigh differently), or misunderstanding (people talking past each other, with what each side seems to mean).
  4. Note changes of position over the thread and proposals for compromise.
  5. Open questions and the information that would help settle them.
  6. Where it stands: whether there is rough consensus, a clear majority of participants, or an open split; and any decision already announced by someone with authority, quoted. Do not recommend a side.
constraints
  • Stay neutral: no recommendation, no rating of arguments as good or bad, and equal care in stating each position. Use neutral wording, not either side's loaded terms.
  • Attribute arguments only to the people who made them; do not invent quotes, data or participants. Short quotes only where the exact wording matters.
  • Count participants, not messages, when describing support, and say if the thread is unlikely to represent everyone affected (for example only maintainers commented).
  • Leave out personal attacks and off-topic exchanges, but note in one line if the tone affected participation.
output format

The question

One sentence (and any secondary questions).

Positions

For each: a heading with the name, the statement, held by (names, count), arguments, objections and replies.

Common ground

Bullets.

Cruxes

Table: Disagreement | Type (factual / values / misunderstanding) | What would resolve it.

Open questions

Bullets.

Where it stands

Two or three sentences, neutral.

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
Productivity and personal life
category
Summarisation
level
Intermediate
made for
Open-source maintainer, Tech lead / staff engineer, Product manager, Anyone, personal use
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 summarize-discussion-positions --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill summarize-discussion-positions -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the productivity plugin
claude plugin install hodios-productivity@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Summarisation
PromptSummarisation

Summarise an email thread

Summarises a long email thread into where things stand now, the decisions made, open questions and who owes what to whom, so you can catch up or reply in minutes.

summarize-email-thread
PromptSummarisation

Summarise a long document

Produces a layered summary of a long document, from one line to key points to section detail, keeping numbers, hedges and nuance faithful and pointing to where each point comes from.

summarize-long-document
PromptSummarisation

Compare two documents

Compares two versions of a document, or two related documents, and reports what changed, what stayed consistent and what conflicts, with quotes and locations for every finding.

compare-documents
PromptSummarisation

Brief me on an unfamiliar topic

Gets someone up to speed on an unfamiliar topic before a meeting or decision, with key terms, main players, live debates, common misconceptions and smart questions, flagging what may be out of date.

brief-me-on-topic
PromptSummarisation

Build a news digest

Turns several articles into a short briefing - key developments, where sources agree or disagree, what is genuinely new and what to watch next - with every point traced to its source.

build-news-digest
PromptSummarisation

Build a timeline from documents

Builds a dated chronology of events from emails, letters and notes with a source for each entry, and flags conflicting dates and gaps. For disputes, claims, complaints and investigations.

build-timeline-from-documents