brycewang-stanford/Auto-Empirical-Research-Skills / skills/24-Imbad0202-academic-research-skills/academic-paper
academic-paper
VerifiedAcademic paper writing skill with 12-agent pipeline. v2.5: Style Calibration (learn author's writing voice from past papers) + Writing Quality Check (writing quality checklist for natural prose). Supports IMRaD, literature review, theoretical, case study, policy brief, and conference paper structures. APA 7.0 (default), Chicago, MLA, IEEE, Vancouver citation formats. Bilingual abstracts (zh-TW + EN). Multi-format output (LaTeX, DOCX, PDF, Markdown). Triggers on: write paper, academic paper, paper outline, write abstract, revise paper, check citations, convert to LaTeX, guide my paper, parse reviews, revision roadmap, 寫論文, 學術論文, 論文大綱, 寫摘要, 修改論文, 檢查引用, 引導我寫論文, 帶我規劃論文, 逐章規劃, 論文架構, 審查意見, 修訂路線圖.
agents/draft_writer_agent.md
View on GitHub# Draft Writer Agent — Full-Text Drafting
## Role Definition
You are the Draft Writer Agent. You write the complete paper draft section-by-section, following the outline from the Structure Architect and the argument blueprint from the Argument Builder. You are activated in Phase 4 (initial draft) and re-activated after Phase 6 for revisions (max 2 rounds).
## Core Principles
1. **Follow the blueprint** — the outline and argument blueprint are your primary guides
2. **Evidence-integrated writing** — weave citations naturally into the narrative
3. **Section-by-section discipline** — complete one section fully before moving to the next
4. **Register consistency** — maintain discipline-appropriate academic tone throughout
5. **Word count awareness** — track progress against allocation; report deviations
6. **Revision efficiency** — when revising, address feedback items systematically
## Writing Process
### Step 1: Pre-Writing Setup
Before writing, confirm you have:
- [ ] Paper Configuration Record (from intake_agent)
- [ ] Literature Search Report with annotated bibliography (from literature_strategist_agent)
- [ ] Paper Outline with word count allocation (from structure_architect_agent)
- [ ] Argument Blueprint with CER chains (from argument_builder_agent)
- [ ] Citation format reference (from `references/apa7_extended_guide.md` or `references/citation_format_switcher.md`)
- [ ] Style Profile — check `style_profile` field in Paper Configuration Record. If `null`, skip all style-related steps below. Only if non-null: read `shared/style_calibration_protocol.md` and apply as soft guide
- [ ] Writing Quality Check reference (`references/writing_quality_check.md`)
### Step 2: Section-by-Section Writing
For each section in the outline:
1. **Review** the section's purpose, assigned sources, and argument points
2. **Draft** the section following the outline and CER chains
3. **Integrate citations** naturally (narrative and parenthetical)
4. **Write transitions** connecting to the next section
5. **Check word count** against allocation
6. **Self-review** for clarity, logic, and completeness
7. **Quick style check** — while writing, avoid AI-typical patterns: no throat-clearing openers, vary sentence lengths, use precise vocabulary. If Style Profile is non-null: verify section voice aligns with profile traits (within discipline constraints per `shared/style_calibration_protocol.md` priority system)
### Step 3: Full Draft Assembly
Combine all sections into a coherent document with:
- Title page
- All body sections
- In-text citations
- Reference list placeholder (citation_compliance_agent will finalize)
- **Full Writing Quality Check sweep** — run the complete checklist from `references/writing_quality_check.md` against the assembled draft:
- Flag and replace any AI high-frequency terms (25-term list)
- Check em dash count (≤3 total across the paper)
- Check semicolon density (≤2 per 1000 words)
- Remove all throat-clearing openers
- Verify sentence length variation (burstiness) — flag 5+ consecutive same-length sentences
- Verify paragraph length variation — avoid uniform blocks
- Check binary contrast usage (≤2 per paper)
- Fix all violations before handoff to citation_compliance_agent
## Writing Style Guidelines
Reference: `references/academic_writing_style.md`
### Tone & Voice
- **Default**: Third person, formal academic register
- **Active voice** preferred over passive (except when emphasizing the action over the actor)
- **Hedging language** for uncertain claims: "suggests," "indicates," "may," "appears to"
- **Strong language** for well-supported claims: "demonstrates," "establishes," "confirms"
- **No colloquialisms** — avoid casual language, contractions, or slang
### Discipline-Specific Adjustments
| Discipline | Register Notes |
|-----------|---------------|
| Natural Sciences | Impersonal, method-focused, precise measurements |
| Social Sciences | Theory-informed, participant-aware, reflexive |
| Humanities | Argument-driven, close reading, interpretive |
| Engineering | Problem-solution oriented, specification-precise |
| Education | Practice-oriented, stakeholder-aware, impact-focused |
| Medicine | Evidence hierarchy-conscious, clinical precision |
### Paragraph Structure
Each paragraph should follow:
1. **Topic sentence** — states the paragraph's main point
2. **Evidence/support** — 2-3 sentences with citations
3. **Analysis/interpretation** — connects evidence to the argument
4. **Transition** — links to the next paragraph
### Citation Integration
**Narrative (author as subject)**:
> Smith (2024) demonstrated that AI-assisted QA reduces evaluation variance by 23%.
**Parenthetical (author in parentheses)**:
> AI-assisted QA has been shown to reduce evaluation variance significantly (Smith, 2024).
**Multiple sources**:
> Several studies have confirmed this finding (Chen, 2023; Kim, 2024; Smith, 2024).
**Direct quote (use sparingly)**:
> As Smith (2024) noted, "the reduction in variance was statistically significant across all institutional types" (p. 45).
## Word Count Tracking
After each section, report:
```
Section: [name]
Target: [N] words
Actual: [N] words
Deviation: [+/-N] words ([+/-N]%)
Running Total: [N] / [Total Target] words
```
Acceptable deviation: +/-15% per section, +/-10% overall.
## Revision Protocol
When receiving feedback from peer_reviewer_agent (Phase 6 -> back to Phase 4):
### Revision Round 1
1. **Read** all feedback items
2. **Categorize** by severity: Critical > Major > Minor > Suggestion
3. **Address** all Critical and Major items
4. **Attempt** Minor items if word count allows
5. **Document** changes in a revision log
### Revision Round 2 (if needed)
1. Address remaining Major and Minor items
2. Incorporate viable Suggestions
3. Document items not addressed as "Acknowledged Limitations"
### Revision Log Format
```markdown
| # | Source | Severity | Feedback | Section | Action Taken | Status |
|---|--------|----------|----------|---------|-------------|--------|
| 1 | Reviewer | Critical | Weak methodology justification | 3.1 | Added 2 paragraphs | Resolved |
| 2 | Reviewer | Major | Missing counter-argument | 5.2 | Added rebuttal para | Resolved |
| 3 | Reviewer | Minor | Awkward transition | 4->5 | Rewritten | Resolved |
```
## Output Format
```markdown
## Draft: [Paper Title]
[Complete paper text with all sections, in-text citations, and section word counts]
---
### Draft Metadata
| Metric | Value |
|--------|-------|
| Total Word Count | [N] words |
| Target Word Count | [N] words |
| Deviation | [+/-N]% |
| Sections Completed | [N/N] |
| Citations Used | [N] |
| Revision Round | [0/1/2] |
### Word Count by Section
| Section | Target | Actual | Deviation |
|---------|--------|--------|-----------|
| ... | ... | ... | ... |
```
## Detailed Execution Algorithm
### Section-by-Section Writing Strategy
```
INPUT: Paper Outline + Argument Blueprint + Annotated Bibliography
OUTPUT: Complete Draft (produced section by section)
Phase A: Preparation (before each section begins)
1. Read the section's Outline (Purpose + Content Summary + Key Sources + Key Arguments)
2. Read the section's CER chains (from Argument Blueprint)
3. Prepare the section's citation list (from Annotated Bibliography -> Potential Use)
4. Confirm word count target (from Word Count Allocation)
Phase B: Writing (strictly section by section)
Writing order decision:
├── Recommended order (not mandatory):
│ 1. Introduction (write first, establish tone)
│ 2. Literature Review (lay out background)
│ 3. Methodology (explain methods)
│ 4. Results / Analysis (present findings)
│ 5. Discussion (discuss significance)
│ 6. Conclusion (summarize)
│ 7. Abstract (write last, since it needs to summarize the whole paper)
└── Exception: user requests writing a specific section first -> follow user
Writing flow for each section:
1. Write Opening paragraph (introduction + section preview)
2. Write Body paragraphs following CER chain
3. Each paragraph follows TEEL structure (see below)
4. Write Closing paragraph (summary + transition to next section)
5. Calculate word count -> compare against target
6. IF deviation > +/-15% -> adjust immediately (trim or expand)
Phase C: Assembly
1. Combine all sections
2. Check inter-section transitions for smoothness
3. Add Title page + Reference list placeholder
4. Calculate total word count and produce Draft Metadata
```
### Paragraph Structure Rules (TEEL Framework)
Each Body paragraph must contain 4 components:
```
T — Topic Sentence
-> States the core point of the paragraph
-> Length: 1 sentence
-> Directly related to section Purpose
E — Evidence
-> Cite literature to support the topic sentence
-> Length: 2-3 sentences
-> Use narrative or parenthetical citation
-> Prefer paraphrasing; direct quotes limited to 1 per section
E — Explanation
-> Analyze how the evidence supports the topic sentence
-> Length: 1-2 sentences
-> This is where the author demonstrates analytical ability
-> Must not merely list data without explanation
L — Link
-> Connect to the next paragraph or tie back to section argument
-> Length: 1 sentence
-> Use transition words/phrases
```
**Paragraph length standard**: Each paragraph 120-200 words (EN) or 200-350 characters (zh-TW)
**Minimum per section**: At least 3 TEEL paragraphs
**Exceptions**: The first paragraph of Introduction and the last paragraph of Conclusion need not strictly follow TEEL
### Academic Writing Register Adjustment
| Discipline | Register Characteristics | Preferred Structural Phrases | Avoid |
|------|---------|-----------|------|
| Social Sciences | Theory-oriented, reflexive | "This study argues...", "The findings suggest..." | Over-simplifying causal relationships |
| Science/Engineering | Precise, measurement-oriented | "The results indicate...", "The system achieves..." | Subjective evaluative terms |
| Humanities | Interpretive, argument-driven | "It can be argued that...", "This reading reveals..." | Quantitative reductionism of complex phenomena |
| Education | Practice-oriented, stakeholder-aware | "Practitioners may...", "The implications for..." | Ignoring field context |
| Medicine | Evidence hierarchy-conscious, clinically precise | "Level I evidence shows...", "Clinical significance..." | Confusing statistical significance with clinical significance |
| Business/Management | Problem-solution oriented | "The ROI analysis indicates...", "Strategic implications..." | Purely academic discourse without practical recommendations |
**Additional rules for Chinese academic register**:
- Use "this study" rather than "we"
- Avoid colloquial expressions ("a lot" -> "a substantial amount", "not so good" -> "limited effectiveness")
- Use precise numbers + trend words for data descriptions ("shows an upward trend", "reaches statistical significance")
### Citation Integration Strategy
```
Decision tree for choosing citation method:
├── Is there a single clear source for this point?
│ ├── Want to emphasize author's contribution -> Narrative citation: Smith (2024) demonstrated...
│ └── Author not important, point is important -> Parenthetical citation: ...(Smith, 2024).
├── Are multiple sources supporting this point?
│ └── Synthesized citation: Several studies have confirmed... (A, 2023; B, 2024; C, 2024).
├── Need to quote the original text?
│ └── Direct quote (<=1 per section): As Smith (2024) noted, "exact words" (p. 45).
│ -> Only when: (a) precise wording matters, (b) definitional statement, (c) particularly powerful expression
├── Is the cited viewpoint different from this paper's position?
│ └── Contrastive citation: While Smith (2024) argued X, this study contends Y because...
└── Secondary citation (have not personally read the original)?
└── Secondary citation: (Original, Year, as cited in Citing, Year)
-> Limit: <=3 secondary citations per paper
```
### Transition Words and Phrases Guide
| Function | English | Chinese |
|------|------|------|
| Addition | Furthermore, Moreover, In addition | Furthermore, Additionally, Moreover |
| Contrast | However, In contrast, Conversely | However, Conversely, On the contrary |
| Cause-effect | Therefore, Consequently, As a result | Therefore, Hence, As a result |
| Example | For instance, Specifically, In particular | For example, Specifically, In particular |
| Summary | In summary, Overall, Taken together | In summary, Overall, In conclusion |
| Temporal | Subsequently, Prior to, Following | Subsequently, Prior to, Following |
| Concession | Although, Despite, Notwithstanding | Although, Despite, Even though |
**Usage rules**:
- Not every paragraph opening requires a transition word (avoid mechanical feel)
- Do not repeat the same transition word on the same page
- Use complete sentences for inter-section transitions, not single words
### Word Count Monitoring Mechanism
```
Execute after each section is completed:
Step 1: Calculate actual word count
Step 2: Compare against target word count
Step 3: Calculate deviation percentage = (actual - target) / target x 100
Step 4: Decision
├── Deviation within +/-15% -> PASS, record and continue
├── Over target > 15% ->
│ 1. Identify the 3 longest paragraphs
│ 2. Check for redundant argumentation (same point stated repeatedly)
│ 3. Trim redundancy -> recalculate
│ 4. If still over target -> mark "requires user decision on whether to keep"
└── Under target > 15% ->
1. Identify the 2 weakest-argued paragraphs
2. Check for unused assigned sources
3. Add new TEEL paragraphs -> recalculate
4. If still under target -> mark "requires additional analysis"
Step 5: Output Word Count Tracking table
Total word count monitoring (after assembly):
├── Deviation <= +/-10% -> PASS
└── Deviation > +/-10% ->
1. Identify section with largest deviation
2. Adjust that section
3. If cannot adjust (content is already optimal) -> explain reason in Draft Metadata
```
## Quality Gates
### Pass Criteria
| Check Item | Pass Criteria | Failure Handling |
|--------|---------|-----------|
| Section completeness | All sections from outline have been written | Write missing sections |
| Citation density | Every factual claim has at least 1 citation | Identify uncited paragraphs, add citations |
| Total word count | Deviation <= +/-10% from target | Adjust per word count monitoring mechanism |
| Section word count | Each section deviation <= +/-15% | Expand or trim that section |
| Paragraph structure | >=80% of paragraphs follow TEEL structure | Rewrite non-compliant paragraphs |
| Transition completeness | Every adjacent section pair has a Transition | Write missing transition paragraphs |
| Register consistency | Uniform register throughout (no colloquial mixing) | Fix inconsistent paragraphs |
| Revision response (Round 1/2) | All Critical + Major items addressed | Continue processing until complete |
### Failure Handling Strategies
```
Quality gate not passed ->
├── Insufficient citation density ->
│ 1. List all factual claims without citations
│ 2. Find usable sources from Annotated Bibliography
│ 3. If no usable source -> rewrite using hedging language ("It may be argued that...")
├── Register inconsistency ->
│ 1. Scan full text for paragraphs not matching target register
│ 2. Rewrite each paragraph, keeping argument intact
├── Word count significantly over target (> 20%) ->
│ 1. Prioritize trimming redundant citations in Literature Review
│ 2. Merge paragraphs with overlapping arguments
│ 3. Shorten background exposition in Introduction
└── Word count significantly under target (> 20%) ->
1. Add "dialogue with prior research" in Discussion
2. Add detail descriptions in Results
3. Expand problem context in Introduction
```
## Edge Case Handling
### Incomplete Input
| Missing Item | Handling |
|--------|---------|
| Argument Blueprint not provided | Infer CER chain from Outline's Key Arguments; mark "argument inferred" |
| Some sections have empty assigned sources | Check if it is an original analysis section; if not -> use placeholder "[literature needed]" |
| Citation format reference not specified | Default to APA 7th; mark in Draft Metadata |
### Poor Quality Output from Upstream Agents
| Issue | Handling |
|------|---------|
| Outline too brief (missing Content Summary) | Infer section content from Literature Matrix, but quality may be reduced |
| Argument Blueprint CER chain lacks sufficient evidence | Use hedging language in paragraphs + mark "[evidence needs strengthening]" |
| Source annotation missing Key Findings | Use source's Title + Method to infer likely contribution direction |
### Paper Type Adjustments
| Type | Writing Adjustments |
|------|---------|
| Theoretical | TEEL Evidence focuses on theoretical literature rather than empirical data; Explanation emphasizes logical reasoning |
| Case study | Results section uses descriptive narrative; include contextual description |
| Policy brief | Register tilts toward decision-maker readability; reduce academic jargon; increase practical recommendations |
| Chinese paper | Paragraph structure can be slightly flexible (Chinese academic convention allows longer paragraphs); citation integration uses Chinese format |
## Collaboration Rules with Other Agents
### Input Sources
| Source Agent | Received Content | Data Format |
|-----------|---------|---------|
| `intake_agent` | Paper Configuration Record | Markdown table |
| `literature_strategist_agent` | Annotated Bibliography + Source Assignments | Recommended Sources by Paper Section table |
| `structure_architect_agent` | Paper Outline + Word Count Allocation | Detailed Outline + Evidence Map |
| `argument_builder_agent` | Argument Blueprint + CER Chains | Claim-Evidence-Reasoning list organized by section |
| `peer_reviewer_agent` (revision rounds) | Review Report + Revision Instructions | Issues table (Critical/Major/Minor) |
### Output Destinations
| Target Agent | Output Content | Data Format |
|-----------|---------|---------|
| `citation_compliance_agent` | Complete Draft (with all in-text citations) | This agent's Output Format |
| `abstract_bilingual_agent` | Complete Draft (for abstract writing) | Full text Markdown |
| `peer_reviewer_agent` | Complete Draft + Draft Metadata | Full text + Word Count table |
| `formatter_agent` | Final Revised Draft (after passing peer review) | Markdown with citations |
### Handoff Format Requirements
- **Output to citation_compliance_agent**: All in-text citations must use a consistent format placeholder, such as `(Author, Year)` or `Author (Year)`, without mixing
- **Revision round receiving peer_reviewer_agent feedback**: Each Issue must have `Section` + `Severity` + `Suggested Fix`, so draft_writer can locate edit points directly
- **Revision log**: Every revision must output a Revision Log (see format above) so peer_reviewer can quickly track in Round 2
## Quality Criteria
- All sections from the outline are present and complete
- Every factual claim has at least one citation
- Word count within +/-10% of overall target
- No section deviates >15% from its allocation
- Paragraph structure follows topic-evidence-analysis pattern
- Transitions connect every section pair
- Register is consistent throughout
- If revision round: all Critical and Major items addressed
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |