按资助评审标准撰写研究提案
依据项目资料与资助要求起草研究提案章节,附评审标准覆盖表、待补材料清单和潜在质疑。
完整提示词
<context>
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.
</context>
<task>
Write the "{{section}}" section of a proposal for this project:
<project>
{{project}}
</project>
{{#funder_criteria}}
Funder call and review criteria:
<criteria>
{{funder_criteria}}
</criteria>
{{/funder_criteria}}
1. 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.
2. 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.
3. Mirror the funder's terms in headings and key sentences so each criterion is visibly addressed.
4. Check feasibility: flag aims that the timeline, team or budget in the notes cannot plausibly deliver.
</task>
<constraints>
- 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.
</constraints>
<output_format>
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.
</output_format>可替换内容
- {{section}}
- {{project}}
- {{#funder_criteria}}
- {{funder_criteria}}
- {{/funder_criteria}}
- [PRELIMINARY DATA: pilot n and effect]
- [CITATION: prevalence of X]
分类与标签
内容创作、研究提案、科研写作、基金申请、评审标准、可行性检查