researchwrite

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

researchwrite — proposal-first 科研写作 pipeline

researchwrite — Proposal-first Scientific Writing Pipeline

受 autonovel(状态机+打分)、professor(动态专家)、brainstorming(入口追问)、anti-AI-writing(语言清理)启发的科研写作状态机。不是通用"帮我写论文"prompt。
A scientific writing state machine inspired by autonovel (state machine + scoring), professor (dynamic experts), brainstorming (entry-level questioning), and anti-AI-writing (language cleaning). Not a general "help me write a paper" prompt.

核心原则

Core Principles

  1. 证据先于文字 — 起草前必须建立或读取
    research_canon
    evidence_table
  2. 论证先于章节 — 写正文前必须完成
    argument_map
  3. 契约先于段落 — 每节需要 purpose / allowed claims / forbidden claims / inputs / validation
  4. 范围先于完备 — 如果是分阶段写作,先锁定阶段边界
  5. 动态专家,不设固定池 — 用
    professor
    按失败模式召唤对应专家
  6. 内容先于语言 — 诊断科学逻辑后再做 anti-slop / 语言打磨
  7. 不自动升级事实 — 永远不把 "may indicate" 改成 "proves",除非有证据支撑
  8. 删除胜于解释 — 当某主张不可行,直接删除。正文干净,解释留给答辩
  9. 该停就停 — 平台期、专家冲突、证据缺失是停止理由,不是润色理由
  1. Evidence Before Prose — Must establish or read
    research_canon
    and
    evidence_table
    before drafting
  2. Argument Before Sections — Must complete
    argument_map
    before writing the main text
  3. Contracts Before Paragraphs — Each section requires purpose / allowed claims / forbidden claims / inputs / validation
  4. Scope Before Completeness — If writing in phases, first lock the phase boundaries
  5. Dynamic Experts, No Fixed Pool — Use
    professor
    to summon corresponding experts based on failure modes
  6. Content Before Language — Diagnose scientific logic before performing anti-slop / language polishing
  7. No Automatic Fact Upgrading — Never change "may indicate" to "proves" unless supported by evidence
  8. Deletion Over Explanation — When a claim is not feasible, delete it directly. Keep the main text clean; leave explanations for defense
  9. Know When to Stop — Plateau periods, expert conflicts, and missing evidence are reasons to stop, not to polish

模式分派

Mode Assignment

输入模式
题目、方向、模糊想法
compose
— 加载
references/compose-mode.md
已有段落/章节/完整 proposal
revise
— 加载
references/revise-mode.md
已有草稿 + 扩写/补写/重构
hybrid
— 加载
references/hybrid-mode.md
模糊时推断默认模式。只在选择会改变工作流时才问用户。
InputMode
Topic, direction, vague ideas
compose
— Load
references/compose-mode.md
Existing paragraphs/sections/complete proposal
revise
— Load
references/revise-mode.md
Existing draft + expansion/supplementation/restructuring
hybrid
— Load
references/hybrid-mode.md
Infer the default mode when ambiguous. Only ask the user if the choice will change the workflow.

项目结构

Project Structure

工作目录
<outputs>/researchwrite/<project-slug>/
标准文件
00_scope.md              写作任务边界
01_research_canon.md     硬事实和约束
02_evidence_table.md      claim → evidence 映射表
03_argument_map.md        论证架构
04_section_contracts.md   每节的 purpose / inputs / allowed & forbidden claims
05_style_guide.md         风格、术语、禁用表达
state.json                项目状态(mode、round、scores、technical_debts)
sources/                  用户材料、文献、数据
drafts/                   草稿和分节文件
revision_briefs/          修订简报
qa_logs/                  诊断、专家审查、anti-slop、打分记录
exports/                  最终输出(.md + .docx)
新建项目时从
templates/
取空模板。
references/worked-example-quaternary-proposal.md
提供了基于通用材料科学领域的完整填写示例。
Working Directory:
<outputs>/researchwrite/<project-slug>/
Standard Files:
00_scope.md              Writing task boundaries
01_research_canon.md     Hard facts and constraints
02_evidence_table.md      claim → evidence mapping table
03_argument_map.md        Argument framework
04_section_contracts.md   Purpose / inputs / allowed & forbidden claims for each section
05_style_guide.md         Style, terminology, prohibited expressions
state.json                Project status (mode, round, scores, technical_debts)
sources/                  User materials, literature, data
drafts/                   Drafts and section files
revision_briefs/          Revision briefs
qa_logs/                  Diagnosis, expert reviews, anti-slop, scoring records
exports/                  Final outputs (.md + .docx)
When creating a new project, take empty templates from
templates/
.
references/worked-example-quaternary-proposal.md
provides a fully filled example based on the general materials science field.

Reference 文件索引

Reference File Index

公开版本包含四个关键 reference:
Reference用途
references/evaluation-rubric.md
8 维 × 4 锚点评分体系 + 评分流程
references/stopping-rules.md
迭代循环终止条件
references/foundation-files.md
建立 foundation 五文件
references/validation-checklist.md
自动校验清单
完整 reference 文件(compose/revise/hybrid 模式详解、专家分派、导出归档、综述框架等 12 份)未包含在公开版本中。如需获取,请通过 GitHub issue 或邮件联系作者。
The public version includes four key references:
ReferencePurpose
references/evaluation-rubric.md
8-dimension × 4-anchor scoring system + scoring process
references/stopping-rules.md
Iteration loop termination conditions
references/foundation-files.md
Establish the five foundation files
references/validation-checklist.md
Automatic validation checklist
The complete reference files (12 documents including detailed explanations of compose/revise/hybrid modes, expert assignment, export archiving, review framework, etc.) are not included in the public version. To obtain them, please contact the author via GitHub issue or email.

运行交付

Running Delivery

每次运行结束时输出:
  1. 当前文件路径或修订后文本
  2. 当前分数/状态
  3. 剩余风险
  4. 一条建议的下一步
At the end of each run, output:
  1. Current file path or revised text
  2. Current score/status
  3. Remaining risks
  4. A suggested next step

QA Mode — 四层质量保障 Pipeline

QA Mode — Four-layer Quality Assurance Pipeline

当用户说"审查这段/跑 QA/检查方案/过 pipeline"时,进入 QA 模式。
Enter QA mode when the user says "review this section/run QA/check the plan/go through the pipeline".

情境挡位

Scenario Gears

挡位适用场景阈值
paper
投稿论文7.0
proposal
研究方案/开题7.0
internal
内部汇报/周报5.0
quick
快速扫读
GearApplicable ScenarioThreshold
paper
Submitted paper7.0
proposal
Research proposal/thesis proposal7.0
internal
Internal report/weekly report5.0
quick
Quick scanNone

Pipeline 顺序(先内容后语言)

Pipeline Order (Content Before Language)

Gate 2: professor Convener(内容层)
  ├── 论文 → 方法论专家 + 领域专家
  ├── proposal → 可行性专家 + 创新性专家
  └── 文献reviews → 覆盖面专家 + 批判深度专家
Gate 1: avoid-ai-writing 模式 detect-only
  └── 只对英文有效,中文跳过或降级为手工扫读
Gate 3: auto-validation(格式/完整性层)
  └── 每个 claim 有 citation?方法可复现?编号连续?
Gate 4: 评分阈值(分维度打分)
  ├── 总分≥阈值 → 通过 ✅
  └── 总分<阈值 → 按低分维度定向回退(不超过 3 轮)
Gate 2 在 Gate 1 之前 — 避免改了句子后被专家打回重写。
Gate 2: Professor Convener (Content Layer)
  ├── Paper → Methodology expert + Domain expert
  ├── Proposal → Feasibility expert + Innovation expert
  └── Literature reviews → Coverage expert + Critical depth expert
Gate 1: avoid-ai-writing mode (detect-only)
  └── Only valid for English; skip or downgrade to manual scanning for Chinese
Gate 3: Auto-validation (Format/Completeness Layer)
  └── Does each claim have a citation? Is the method reproducible? Are numbers consecutive?
Gate 4: Scoring Threshold (Dimension-based Scoring)
  ├── Total score ≥ threshold → Pass ✅
  └── Total score < threshold → Directed rollback based on low-score dimensions (no more than 3 rounds)
Gate 2 comes before Gate 1 — Avoid rewriting sentences only to be sent back by experts.

使用方法

Usage Examples

用户: "用 researchwrite 审查这段 discussion,paper 挡位"
  → 自动走 Gate 2 → Gate 1 → Gate 3 → Gate 4
  → 返回审查报告 + 定向修改建议

用户: "快速扫一下这个邮件"
  → 走 quick 挡位,只标记 P0 问题
User: "Review this discussion section with researchwrite, paper gear"
  → Automatically go through Gate 2 → Gate 1 → Gate 3 → Gate 4
  → Return review report + targeted modification suggestions

User: "Quickly scan this email"
  → Use quick gear, only mark P0 issues

配置你的研究域

Configure Your Research Domain

首次使用告诉 agent 你的研究背景,agent 会调用
professor
建立领域专家知识。后续写作中专家审查会基于你的领域。
Tell the agent your research background on first use, and the agent will call
professor
to establish domain expert knowledge. Subsequent expert reviews during writing will be based on your field.