hermes

Write a discussion section

Writes a paper or thesis discussion covering principal findings, comparison with prior work, mechanisms, limitations, implications and future work, matching claims to the evidence. For authors.

context

A discussion interprets the results; it does not repeat them. Reviewers look for a clear statement of what was found, an honest comparison with what others found and why results might differ, plausible explanations offered as explanations rather than facts, limitations that say how they could have changed the result, and implications that do not outrun the design. The most common problems are overclaiming (causal language from observational data, generalising beyond the sample, treating non-significant results as proof of no effect), listing limitations without saying their likely impact, and a "future research is needed" ending with no specifics.

task

Write a discussion of about words from these results.

results

Only if [PRIOR_LITERATURE] is given:

prior literature

  1. Principal findings: open with the answer to the research question in two or three sentences, using the key numbers, without restating all results.
  2. Comparison with prior work: for each main finding, say whether it agrees or disagrees with the prior studies supplied and give plausible reasons for differences (population, design, measures, timing, power). Cite only the supplied studies. If none were supplied, write [CITE: studies on …] placeholders describing what kind of evidence is needed.
  3. Possible explanations: offer mechanisms or interpretations, labelled as possible ("one explanation is…"), with what evidence would test them.
  4. Strengths and limitations: the real strengths of the design, then each limitation with its likely direction and size of effect on the results (for example "non-response was higher among smokers, which would probably bias the association towards the null").
  5. Implications: for research, practice or policy as the design supports. Match the strength of the recommendation to the strength of the evidence.
  6. Future work: two or three specific studies that would resolve the main uncertainty.
  7. Conclusion: two or three sentences that a reader could quote without misrepresenting the study.

Then check your own draft: list each claim that goes beyond the data and how you softened it.

constraints
  • Use only the numbers in the results. Never invent statistics or findings.
  • Match language to design: "associated with" for observational data unless a causal design justifies more; "we found no evidence of a difference" rather than "there is no difference" for non-significant results, with the confidence interval where available.
  • Do not introduce new results that are not in the results section.
  • Never cite a study that was not supplied, and never attribute findings to a supplied study beyond what the user wrote about it.
  • Hedge where evidence is uncertain, but do not hedge every sentence into meaninglessness.
  • If the results text lacks the research question or design, ask for them or state your assumption at the top.
output format

Discussion

The section, with optional subheadings (Principal findings, Comparison with other studies, Strengths and limitations, Implications, Conclusion) as the target journal or thesis expects.

Claims check

Table: claim in the draft | evidence for it | adjustment made.

Citations to add

Each [CITE: …] placeholder and what kind of source would fill it.

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
Research and science
category
Scientific writing
level
Intermediate
made for
Researcher / scientist, Student
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-02
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 write-discussion-section --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill write-discussion-section -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the research-science plugin
claude plugin install hodios-research-science@hodios

The plugin brings every entry in this domain at once.

PromptScientific writing

Write a replicable methods section

Writes a manuscript methods section another researcher could replicate, following the relevant reporting guideline and flagging every missing detail. For authors drafting a paper or thesis.

write-methods-section
PromptScientific writing

Write a paper abstract

Writes a structured or unstructured abstract within a word limit from a manuscript, keeping every number faithful to the source and showing where each appears. Use before submission.

write-abstract
PromptScientific writing

Respond to peer reviewers

Drafts a point-by-point response to peer-review comments, giving the change made or a polite, evidenced rebuttal for each, never claiming unmade changes. Use for revise-and-resubmit.

respond-to-reviewers
PersonaResearch methods

Research methodologist

Research methodologist who probes study designs for validity threats, matches methods to questions and asks what evidence would change the conclusion. Use as a sparring partner for any study.

research-methodologist
PersonaScientific writing

Thesis advisor

Acts as a thesis advisor who sharpens the research question, keeps scope realistic, pushes for a clear contribution and sets milestones, with direct, supportive feedback. For graduate students.

thesis-advisor
PromptScientific writing

Explain research to the public

Turns a research paper into an accurate plain-language summary, press release, blog post or social thread without hype, keeping caveats, study type and effect sizes. Use for science communication.

explain-research-to-public