Generate academic research proposals for PhD applications. Use when user asks to "write a research proposal", "create PhD proposal", "generate research plan", "撰写研究计划", "写博士申请", "doctoral proposal", or mentions specific research topics for PhD application. Supports STEM, humanities, and social sciences with field-specific adaptations. Follows Nature Reviews-style academic writing conventions. Supports both English and Chinese output based on user preference.
Generate high-quality academic research proposals for PhD applications following Nature Reviews-style academic writing conventions.
This skill guides the generation of research proposals through a structured 5-phase workflow:
Target Output: 2,000-4,000 words (default ~3,000 words) for PhD applications.
Use AskUserQuestion to collect the following information:
Research Topic/Direction
Academic Domain
Output Language
Target Word Count
Target Institution(s)
Existing Materials
Questions to ask the user:
1. "What is your research topic or direction? Please describe the core question or problem you want to investigate."
2. "Which academic domain does your research belong to?"
- STEM (Science, Technology, Engineering, Mathematics)
- Humanities (History, Philosophy, Literature)
- Social Sciences (Sociology, Psychology, Economics)
3. "What language should the proposal be written in?"
- English
- 中文 (Chinese)
4. "Do you have a target word count? (Default: ~3,000 words)"
5. "Are you applying to specific institutions or working with particular faculty?"
6. "Have you uploaded relevant literature to your Zotero library that I should reference?"
┌─────────────────────────────────────────────────────────┐
│ Literature Sources │
├─────────────────────────────────────────────────────────┤
│ General Info → WebSearch (trends, news, reviews) │
│ Open Access → arXiv, PubMed (preprints, OA papers)│
│ Closed Access → Zotero MCP (user's uploaded papers) │
└─────────────────────────────────────────────────────────┘
Search for:
Example searches:
"{topic} systematic review 2024 2025"
"{topic} research trends future directions"
"{topic} methodology recent advances"
IMPORTANT: Remind users to upload relevant closed-access literature to Zotero before starting.
# Search by topic keywords
Use: mcp__zotero__zotero_search_items
Parameters: query = "{research topic keywords}"
# Advanced search with filters
Use: mcp__zotero__zotero_advanced_search
Parameters: conditions based on author, title, year, tags
# Semantic search for related papers
Use: mcp__zotero__zotero_semantic_search
Parameters: query = "{research question}"
# Get full text content
Use: mcp__zotero__zotero_get_item_fulltext
Parameters: item_key = "{item key from search}"
# Get user's annotations and highlights
Use: mcp__zotero__zotero_get_annotations
Parameters: item_key = "{item key}"
# Get user's notes
Use: mcp__zotero__zotero_get_notes
Parameters: item_key = "{item key}"
Organize collected literature into categories:
Read the reference file for domain-specific guidance:
references/STRUCTURE_GUIDE.md - Detailed section guidelinesreferences/DOMAIN_TEMPLATES.md - STEM vs Humanities differences# [Research Title]
## Abstract (150-300 words, 5-10%)
- Research problem summary
- Research questions/objectives
- Methodology overview
- Expected significance
## 1. Introduction (500-800 words, 15-20%)
### 1.1 Background and Context
### 1.2 Problem Statement
### 1.3 Research Questions/Objectives
### 1.4 Scope and Delimitations
## 2. Literature Review (500-1000 words, 20-25%)
### 2.1 Theoretical Framework
### 2.2 Current State of Research
### 2.3 Research Gap Analysis
### 2.4 Positioning of This Study
## 3. Methodology (500-800 words, 20-25%)
### 3.1 Research Design
### 3.2 Data Collection Methods
### 3.3 Data Analysis Approach
### 3.4 Validity and Limitations
## 4. Timeline (200-300 words, 5-10%)
### 4.1 Research Phases
### 4.2 Key Milestones
### 4.3 Gantt Chart (optional)
## 5. Significance and Expected Contributions (200-400 words, 10-15%)
### 5.1 Theoretical Contributions
### 5.2 Practical Implications
### 5.3 Broader Impact
## References (minimum 40 references)
Note: Do NOT include Appendix sections. All essential content should be integrated into the main body.
CRITICAL: Present the outline to the user and wait for confirmation before proceeding to content generation.
Present the generated outline and ask:
"Here is the proposed outline for your research proposal:
[Display outline with section titles and estimated word counts]
Please review and let me know:
1. Is the overall structure acceptable?
2. Would you like to add, remove, or modify any sections?
3. Should any section receive more/less emphasis?
I will proceed with content generation once you approve the outline."
Read and apply: references/WRITING_STYLE_GUIDE.md
Academic Register
Prose-Based Writing Style (CRITICAL)
AVOID point-by-point enumeration. Academic proposals should read as flowing, connected prose rather than bulleted lists or numbered items. Use transitional phrases and coherent paragraphs to present ideas.
| Avoid | Use Instead |
|---|---|
| Bullet points listing objectives | Integrated paragraph describing objectives with transitions |
| Numbered lists of contributions | Narrative prose explaining contributions in context |
| Tables for methodology steps | Flowing description of research design |
When lists ARE appropriate (use sparingly):
Example transformation:
❌ Poor (point-by-point):
The contributions include:
- Novel segmentation algorithm
- Multi-modal fusion framework
- Clinical validation study
✓ Good (prose-based):
This research is expected to advance the field through several interconnected
contributions. First, the development of a novel segmentation algorithm will
enable automated plaque detection with accuracy surpassing current methods.
Building on this foundation, a multi-modal fusion framework will integrate
complementary imaging data to capture plaque characteristics inaccessible to
any single modality. Finally, rigorous clinical validation will establish
the prognostic value of these computational biomarkers for predicting
cardiovascular events.
Hedging Language (Academic Caution)
| Avoid | Use Instead |
|---|---|
| "will prove" | "aims to demonstrate" |
| "definitely" | "likely", "potentially" |
| "is obvious" | "evidence suggests" |
| "proves" | "indicates", "demonstrates" |
Sentence Templates
Introducing Background:
Identifying Gaps:
Stating Objectives:
Methodology Justification:
Expected Contributions:
Transitions and Connectors
Paragraph Structure
Topic Sentence → Supporting Evidence (with citations) → Synthesis/Implications
Based on domain:
First mention of abbreviations: "coronary CT angiography (CCTA)"
Integrate citations into text: "Recent studies (Smith et al., 2023; Jones, 2024) have demonstrated..."
IMPORTANT: Include suggestions for figures at appropriate locations throughout the proposal. Figures significantly enhance readability and demonstrate the applicant's ability to communicate complex ideas visually.
Insert figure suggestions using the following format:
> **[Figure 1 Suggestion]** *Title: Overview of the proposed research framework*
> Content: A flowchart or schematic diagram illustrating the three-phase research
> design, showing data flow from imaging modalities through AI processing to
> clinical outcomes. Include icons for CCTA/IVUS/OCT inputs, deep learning
> modules, and output predictions.
> Recommended style: Clean vector graphics with consistent color scheme.
| Section | Suggested Figure Type |
|---|---|
| Introduction | Conceptual diagram showing research scope and positioning |
| Literature Review | Timeline of key developments; Taxonomy/classification of existing methods |
| Methodology | Research framework flowchart; Network architecture diagram; Data processing pipeline |
| Timeline | Gantt chart showing research phases and milestones |
| Significance | Impact diagram showing theoretical and practical contributions |
Generate the proposal as a Markdown file:
proposal_{topic_slug}_{YYYY-MM-DD}.md
Save to user's working directory or specified location.
Read and apply: references/QUALITY_CHECKLIST.md
Verify:
After the Markdown proposal is finalized, convert it to a professional PDF using the built-in conversion script.
Run the script via Bash:
python3 /Users/ritingliu/Documents/mini-research/.claude/skills/research-proposal/scripts/md_to_pdf.py <input.md> [output.pdf]
If output.pdf is omitted, it defaults to the same path as the input with .pdf extension.
1., 2., etc.; H3 → 1.1, 1.2, etc.)./image/ directory (relative to the Markdown file)reportlab installed (pip install reportlab)scripts/fonts/ and loaded automatically by the script for native rendering of scientific characters (subscripts ₀-₉, Greek letters α β π σ, arrows →, math operators ≤ ≥ ≈, etc.)python3 scripts/md_to_pdf.py proposal_topic_2026-03-10.md
# -> produces proposal_topic_2026-03-10.pdf
For other formats, users can also use pandoc:
# Convert to Word document
pandoc proposal.md -o proposal.docx
This skill uses the following reference documents:
| File | Purpose |
|---|---|
references/STRUCTURE_GUIDE.md | Detailed section-by-section writing guide |
references/DOMAIN_TEMPLATES.md | STEM vs Humanities structural differences |
references/WRITING_STYLE_GUIDE.md | Nature Reviews academic writing style |
references/QUALITY_CHECKLIST.md | Complete quality verification checklist |
references/LITERATURE_WORKFLOW.md | Literature collection workflow details |
assets/proposal_scaffold_en.md | English template scaffold |
assets/proposal_scaffold_zh.md | Chinese template scaffold |
scripts/md_to_pdf.py | Markdown-to-PDF converter with cover page, clickable TOC, figures |
scripts/fonts/STIXTwoText-Regular.ttf | STIX Two Text — scientific publishing font (regular) |
scripts/fonts/STIXTwoText-Bold.ttf | STIX Two Text — bold variant |
scripts/fonts/STIXTwoText-Italic.ttf | STIX Two Text — italic variant |
scripts/fonts/STIXTwoText-BoldItalic.ttf | STIX Two Text — bold italic variant |
scripts/fonts/STIXTwoMath-Regular.ttf | STIX Two Math — math/symbol fallback (arrows, operators) |
┌──────────────────────────────────────────────────────────────────┐
│ Research Proposal Generation │
├──────────────────────────────────────────────────────────────────┤
│ │
│ Phase 1: Requirements [Interactive] │
│ │ └─ Topic, Domain, Language, Word Count │
│ ▼ │
│ Phase 2: Literature [Automatic] │
│ │ └─ WebSearch + Zotero MCP │
│ ▼ │
│ Phase 3: Outline [Interactive - User Approval Required] │
│ │ └─ Generate outline → User confirms → Proceed │
│ ▼ │
│ Phase 4: Content [Automatic - One-shot Generation] │
│ │ └─ Write all sections based on approved outline │
│ ▼ │
│ Phase 5: Output [Delivery] │
│ │ └─ Markdown file + Quality checklist │
│ ▼ │
│ Phase 6: PDF [Automatic] │
│ └─ scripts/md_to_pdf.py → Cover + TOC + Content PDF │
│ │
└──────────────────────────────────────────────────────────────────┘
If user's Zotero library has no relevant papers:
If topic is too vague:
If content exceeds target: