Write a research proposal
Writes a research or grant proposal section (aims, significance, approach, timeline) mapped to the funder's criteria, with placeholders instead of invented data. Use for grant or thesis proposals.
Reviewers score proposals against published criteria, often in a few minutes per section. Strong proposals make the problem and its stakes obvious in the first paragraph, state aims that are specific, measurable and independent (one failing aim does not sink the others), show the approach is feasible with preliminary evidence and named alternatives, and use the funder's own language so each criterion is easy to score. Weak ones are vague about aims, hide the hypothesis, promise too much for the timeline and leave reviewers to find the answer to each criterion themselves.
Write the "" section of a proposal for this project:
Only if [FUNDER_CRITERIA] is given: Funder call and review criteria:
- Extract the review criteria, limits and required headings from the funder text. Without funder text, use the widely shared criteria of significance, innovation, approach, investigators and environment, and say so.
- Write the requested part:
- aims: an opening paragraph on the problem and the gap, the long-term goal, the objective of this proposal, the central hypothesis and its rationale, then two to four aims, each with a working hypothesis or objective, a one-line approach and the expected outcome, and a closing paragraph on the payoff.
- significance: the problem's size and consequences, what is known and the specific gap, and what will change if the aims succeed, for the field and for people.
- approach: per aim, the rationale, the design and methods, the analysis, expected results, potential problems with alternative strategies, and success benchmarks; then a timeline table by quarter or semester with milestones.
- full: all of the above in the funder's order, within its limits.
- Mirror the funder's terms in headings and key sentences so each criterion is visibly addressed.
- Check feasibility: flag aims that the timeline, team or budget in the notes cannot plausibly deliver.
- Use only facts from the project notes and funder text. For anything missing (preliminary data, figures, citations, budget, collaborators' names), insert a visible placeholder such as "[PRELIMINARY DATA: pilot n and effect]" or "[CITATION: prevalence of X]". Never invent results, numbers or references.
- Respect the funder's limits; if none are given, keep aims to about one page (roughly 500 words) and say what length you assumed for other sections.
- Write in active voice with concrete verbs, and make each aim's success testable.
- Do not overpromise: impact claims must follow from the aims.
- If the project notes are too thin to write a credible section (for example no question or method), ask for the missing pieces first, listing exactly what is needed.
The requested section(s) under the funder's headings, then:
Criteria coverage
A table: criterion | where it is addressed | strength (strong / adequate / weak) | how to strengthen.
Placeholders to fill
A checklist of every placeholder in the draft.
Reviewer risks
Three to five likely reviewer objections, each with the sentence or evidence that would pre-empt 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
- Expert
- made for
- Researcher / scientist, Student
- risk
- read-only
- version
- v1.0.0 · experimental
- reviewed
- 2026-10-02
- 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-research-proposal --target claude-codenpx skills add hermes-hq/hodios-dist --skill write-research-proposal -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-research-science@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of Scientific writingDesign a research study
Designs a study from a research question to hypotheses, design, variables, sampling and sample size, a pre-specified analysis plan and threats to validity. Use before collecting any data.
design-research-studyFind research gaps
Identifies gaps, contradictions and open questions across a set of abstracts or notes, ties each to its sources and turns it into a researchable question. Use when scoping a thesis, grant or review.
find-research-gapsExplain 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-publicRespond 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-reviewersWrite 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-abstractAcademic writing rules
Standing rules for academic writing that hedge claims to the evidence, define terms, forbid invented citations, keep tense and terminology consistent, and report numbers precisely.
academic-writing-rules