rw-phd-write

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

RW PhD Write

根据用户提供的研究材料和可核验来源组织科研文本。先判断当前部分承担什么写作功能，再决定需要哪些证据、解释和连接。

Organize scientific research text based on user-provided research materials and verifiable sources. First determine the writing function of the current section, then decide what evidence, explanations, and connections are needed.

启动

Startup

读取

references/standalone.md

、

references/method.md

、

references/writing-functions.md

和

references/standards.md

。

读取用户本轮提供的材料；没有材料时，只完成当前证据允许的部分。
需要规则判断时检索
```
references/atoms.jsonl
```
；遇到相似任务时读取
```
references/cases.md
```
。
需要选择方法或工具时读取
```
references/domain-guide.md
```
，并使用
```
assets/worksheet.md
```
组织交付。
读取
```
references/acceptance.md
```
。
```
references/behavior-tests.json
```
只用于测试，不作为用户任务事实。
当前文献、API、报告规范和期刊要求可能变化时，打开
```
references/source-map.md
```
中的官方链接核验并记录日期。

Read

references/standalone.md

references/method.md

references/writing-functions.md

and

references/standards.md

Read the materials provided by the user in this session; if no materials are provided, only complete the parts allowed by the current evidence.
Retrieve
```
references/atoms.jsonl
```
when rule judgment is required; read
```
references/cases.md
```
when encountering similar tasks.
Read
```
references/domain-guide.md
```
when selecting methods or tools, and use
```
assets/worksheet.md
```
to organize deliverables.
Read
```
references/acceptance.md
```
.
```
references/behavior-tests.json
```
is only used for testing and not as factual information for user tasks.
When current literature, APIs, report specifications, and journal requirements may change, open the official links in
```
references/source-map.md
```
for verification and record the date.

工作阶段

Work Phases

先建立 research output profile，记录机构、文稿类型、读者、研究问题、语言区域、引用格式、导师或审稿反馈、正向样本、输出格式和公开边界。
依据内容和上下文判断文稿、章节、小节和段落的写作功能，不从章节编号推断功能。
为当前功能确定解释义务：读者需要知道什么、哪些连接必须明说、哪些解释不应出现在这里。
建立 function-to-claim-to-source 表，区分写作功能、目标主张、证据、作者解释、重要性、研究问题连接、限制和未知事项。
按写作功能组织论证移动和段落顺序；先写论点和证据骨架，再写正文，不生成未核验引用。
运行读者推断检查：如果关键结论只能靠读者补出，补写有证据支持的连接；证据不足时标记缺口。
按研究类型检查相应报告规范、方法透明度和披露事项。
运行来源、具体性、因果强度、功能完成度、前后一致性、作者语气和修改范围检查，再把成稿交给引用核验和交付质检。

First establish a research output profile, recording the institution, document type, audience, research questions, language region, citation format, supervisor or reviewer feedback, positive samples, output format, and public boundaries.
Determine the writing functions of the document, chapters, sections, and paragraphs based on content and context, rather than inferring functions from chapter numbers.
Define the explanatory obligations for the current function: what the audience needs to know, which connections must be explicitly stated, and which explanations should not appear here.
Create a function-to-claim-to-source table, distinguishing between writing functions, target claims, evidence, author explanations, significance, connections to research questions, limitations, and unknowns.
Organize the argument flow and paragraph order according to writing functions; first write the skeleton of arguments and evidence, then draft the main text, and do not generate unverified citations.
Conduct audience inference checks: if key conclusions can only be filled in by the audience, add evidence-supported connections; mark gaps when evidence is insufficient.
Check the corresponding report specifications, method transparency, and disclosure items according to the research type.
Perform checks on sources, specificity, causal strength, function completion, consistency, author tone, and revision scope, then submit the draft for citation verification and delivery quality inspection.

运行规则

Operating Rules

写作从章节功能和主张开始，不从漂亮句子开始。
章节编号不是写作功能。同一编号在不同论文中可以承担不同任务。
每个章节、小节和段落都要完成当前写作功能，但不套用同一段落模板。
解释义务由写作功能决定。建立问题、综合文献、提出缺口和解释结果时，通常需要说明证据说明什么、为什么重要、怎样连接研究问题；Results 以准确报告发现为主，不提前写成 Discussion。
连续列出研究结果不能代替综合判断。需要作者判断时，明确写出当前证据允许的解释和边界。
如果关键逻辑只能由作者脑中补全而读者无法从文字获得，补写连接；不能用空泛的“这很重要”代替具体后果。
保留样本、测量、比较、数字、效应、不确定性和原文定位等具体信息，不为增加细节而补造材料。
导师或审稿人的正向评价用于校准证据密度、解释深度和句间连接，不只用于模仿语气。
每个事实性主张都要有用户材料或可核验来源。
来源支持范围小于句子范围时，收窄句子。
结果、解释、推断和建议要使用不同的证据强度。
Introduction 建立问题和缺口，不能提前假定研究结论。
Methods 说明做了什么和为何这样做，不能用结果合理化方法。
Results 报告预定和实际分析，不用 Discussion 语言解释。
Discussion 先回答研究问题，再比较证据、解释限制和外推边界。
报告规范是最低透明度检查，不是段落模板。
用户修改要求优先保留原判断、证据和限制。
没有作者语料时使用克制的学术注册，不冒充个人指纹。
用户已指定可用的持久语气 profile 或本地 tone skill 时，先使用该 profile；没有时再由 rw-phd-tone 从本轮样本建立临时规则。
公开正文不得包含搜索日志、claim audit 路径、draft-status note 或其他内部交接说明。
引用、作者贡献、利益冲突和 AI 使用按目标期刊当前规则核验。

Start writing from chapter functions and claims, not from polished sentences.
Chapter numbers are not writing functions. The same number can serve different purposes in different papers.
Each chapter, section, and paragraph must fulfill its current writing function, but do not apply the same paragraph template.
Explanatory obligations are determined by writing functions. When framing the problem, synthesizing literature, identifying gaps, and explaining results, it is usually necessary to state what the evidence shows, why it is significant, and how it connects to the research questions; Results sections focus on accurately reporting findings and should not be written as Discussion sections in advance.
Listing research results consecutively cannot replace comprehensive judgment. When author judgment is required, clearly state the interpretations and boundaries allowed by the current evidence.
If key logic can only be completed in the author's mind and cannot be obtained by the audience from the text, add connections; do not use vague phrases like "this is important" to replace specific consequences.
Retain specific information such as samples, measurements, comparisons, numbers, effects, uncertainties, and original text locations; do not fabricate materials to add details.
Positive feedback from supervisors or reviewers is used to calibrate evidence density, explanation depth, and inter-sentence connections, not just to mimic tone.
Every factual claim must be supported by user materials or verifiable sources.
When the scope of source support is smaller than the scope of the sentence, narrow the sentence.
Results, interpretations, inferences, and recommendations should use different levels of evidence strength.
The Introduction section frames the problem and identifies gaps, and should not assume research conclusions in advance.
The Methods section explains what was done and why it was done, and should not rationalize methods using results.
The Results section reports planned and actual analyses, and should not use Discussion language for explanations.
The Discussion section first answers the research questions, then compares evidence, explains limitations, and extrapolates boundaries.
Report specifications are minimum transparency checks, not paragraph templates.
User revision requirements take precedence; retain original judgments, evidence, and limitations.
Use a restrained academic register when no author corpus is available; do not impersonate personal writing styles.
When the user has specified an available persistent tone profile or local tone skill, use that profile first; if not, rw-phd-tone will establish temporary rules from the current session's samples.
Public text must not include search logs, claim audit paths, draft-status notes, or other internal handover instructions.
Citations, author contributions, conflicts of interest, and AI usage are verified according to the current rules of the target journal.

输出

Outputs

章节、段落或论证骨架。
research output profile、function-to-claim-to-source 表和引用缺口。
写作功能判断、解释义务、读者推断断点和未完成项。
修改说明、未解决问题和下游核验状态；按任务规模只展开必要部分。

Chapters, paragraphs, or argument skeletons.
Research output profile, function-to-claim-to-source table, and citation gaps.
Writing function judgments, explanatory obligations, audience inference gaps, and incomplete items.
Revision notes, unresolved issues, and downstream verification status; only expand necessary parts according to task scale.

停止条件

Stop Conditions

没有来源时，不生成事实性引用或伪造 DOI。
没有研究结果时，不写成研究已完成。
没有证据支持重要性或研究问题连接时，标记为作者判断或证据缺口，不生成通用意义句。
不为流畅删除限制、反例和不确定性。
不把 Skill 输出当成作者最终责任或期刊合规确认。

Do not generate factual citations or fake DOIs when no sources are available.
Do not write as if the research is completed when no research results are available.
When there is no evidence to support significance or connections to research questions, mark it as author judgment or evidence gap; do not generate generic significance sentences.
Do not remove limitations, counterexamples, or uncertainties for the sake of fluency.
Do not treat Skill output as the author's final responsibility or journal compliance confirmation.

随 Skill 提供的资源

Resources Provided with the Skill

```
assets/research-output-profile.yaml
```
：在写作开始前记录机构、读者、语言、引用、缩写和公开边界。

```
assets/research-output-profile.yaml
```
: Record the institution, audience, language, citations, abbreviations, and public boundaries before starting writing.

独立运行

Standalone Operation

默认不读取私人工作区、个人语料目录或预设 research-lab。
用户提供的文件、文本、链接和数据是当前任务输入，不是安装依赖。
网络不可用时，使用 Skill 内的稳定方法继续；需要当前事实的部分标记为待核验。
本包内其他科研 Skill 存在时可以接续；单独安装时直接返回下一步说明，不停止当前任务。

By default, do not read private workspaces, personal corpus directories, or preset research-labs.
Files, text, links, and data provided by the user are inputs for the current task, not installation dependencies.
When the network is unavailable, continue using stable methods within the Skill; mark parts requiring current facts as pending verification.
Can connect with other scientific research Skills in this package if they exist; when installed alone, directly return instructions for the next step without stopping the current task.

来源纪律

Source Discipline

把用户材料、公开来源、当前推断和未知事项分开。
报告规范只检查报告透明度，不自动证明设计质量。
公开来源摘要保存在 Skill 内；需要版本、费用、政策、API 或期刊现状时回到官方页面。
不生成不存在的论文、数据、DOI、工具运行结果或期刊要求。

Separate user materials, public sources, current inferences, and unknowns.
Report specifications only check report transparency, and do not automatically prove design quality.
Public source abstracts are stored within the Skill; when version, cost, policy, API, or journal status is needed, return to the official page.
Do not generate non-existent papers, data, DOIs, tool operation results, or journal requirements.