academic-research-suite
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAcademic Research Suite for Codex
Codex专属学术研究套件
This is a Codex adapter for the ARS suite. The vendored ARS content lives under
; keep it as source material and route through this file first.
ars/本套件是ARS套件的Codex适配器。ARS相关内容存放在目录下;请将其作为源素材,先通过本文件进行路由。
ars/Versioning
版本控制
This Codex package is version . The repo-root , this
metadata version, and must match.
Vendored ARS suite versions are tracked separately by source repository commit
in .
0.1.7VERSIONSKILL.mdmanifest.jsonadapter_versionmanifest.json本Codex包版本为。仓库根目录的、本的元数据版本以及中的必须保持一致。ARS套件的版本通过中源仓库的提交记录单独跟踪。
0.1.7VERSIONSKILL.mdmanifest.jsonadapter_versionmanifest.jsonFirst Rule
首要规则
Do not load the whole suite by default. Select one workflow, read that workflow's
, then load only the agent, reference, template, or shared files needed
for the user's current stage.
WORKFLOW.mdThe internal workflow entry files are named , not , so
Codex registers only this root router skill instead of exposing every vendored
upstream workflow as a separate skill.
WORKFLOW.mdSKILL.md默认情况下不要加载整个套件。选择一个工作流,阅读该工作流的,然后仅加载用户当前阶段所需的Agent、参考资料、模板或共享文件。
WORKFLOW.md内部工作流入口文件命名为,而非,因此Codex仅注册此根路由技能,不会将每个上游工作流作为单独技能暴露。
WORKFLOW.mdSKILL.mdWorkflow Router
工作流路由
Choose the workflow by intent:
| User intent | Read first |
|---|---|
| Deep research, literature review, systematic review, meta-analysis, fact-checking, research question refinement | |
| Academic paper writing, paper outline, abstract, revision, citation formatting, AI disclosure, LaTeX/DOCX/PDF formatting guidance | |
| Paper review, peer review simulation, editorial decision, reviewer calibration, re-review after revision | |
| End-to-end research-to-paper pipeline, integrity gate, staged review/revision/finalization workflow | |
| Experiment planning, code experiment execution plan, human study protocol, statistical interpretation, reproducibility validation | |
If the request spans multiple workflows, start with
unless the user clearly asked for a single phase.
ars/academic-pipeline/WORKFLOW.md根据用户意图选择工作流:
| 用户意图 | 首先阅读 |
|---|---|
| 深度研究、文献综述、系统综述、元分析、事实核查、研究问题细化 | |
| 学术论文写作、论文大纲、摘要、修改、引用格式、AI披露、LaTeX/DOCX/PDF格式指导 | |
| 论文评审、同行评审模拟、编辑决策、审稿人校准、修改后重审 | |
| 端到端研究转论文流程、完整性检查、阶段性评审/修改/定稿工作流 | |
| 实验规划、代码实验执行计划、人体研究方案、统计解读、可重复性验证 | |
如果用户请求涉及多个工作流,除非用户明确要求单阶段处理,否则从开始。
ars/academic-pipeline/WORKFLOW.mdPaper Topic Scoping Override
论文主题范围覆盖规则
Apply this override before the general paper/pipeline routing rule and before the Claude-Style Alias Router below.
The override applies regardless of whether the user invokes ARS via natural
language or via an alias.
ars-*If the user says they want to write a paper, thesis, proposal, article, journal
article, or manuscript, but they only provide a broad topic, tentative title,
research interest, or "題目/主題/方向" and do not provide a clear,
answerable research question, route to in
mode first. This matches the upstream ARS experience where vague
paper-topic requests start with SCR/Socratic narrowing instead of immediate
outline or drafting.
ars/deep-research/WORKFLOW.mdsocraticTreat these as Socratic triggers even when the wording contains paper-writing
intent:
- "I want to write a paper on ..."
- "I have a paper topic/title ..."
- "我想做一篇論文,題目是..."
- "我有一個研究方向/主題,但還不確定問題"
- "幫我想論文題目/收斂研究問題"
First response in this path:
- State that the request is being routed to
deep-researchmode because the research question is not yet precise.socratic - Ask 3-5 Socratic narrowing questions using and
socratic_mentor_agentguidance.research_question_agent - Do not produce an outline, draft, literature review, or full pipeline dashboard until the user has converged on at least one candidate RQ.
Route directly to only when the user already
has a clear RQ, approved study frame, data/results, literature matrix, draft,
or explicitly asks to skip scoping and proceed to outline/drafting. Route to
only when the user explicitly asks for the
full research-to-paper pipeline or says to continue after Socratic scoping.
ars/academic-paper/WORKFLOW.mdars/academic-pipeline/WORKFLOW.md在通用论文/流程路由规则和下文的Claude风格别名路由规则之前,先应用此覆盖规则。无论用户是通过自然语言还是别名调用ARS,均适用此规则。
ars-*如果用户表示想要撰写论文、学位论文、提案、文章、期刊文章或稿件,但仅提供宽泛主题、暂定标题、研究兴趣或“題目/主題/方向”,且未提供清晰、可解答的研究问题,则先路由至的模式。这与上游ARS的使用体验一致:模糊的论文主题请求会先通过SCR/苏格拉底式收窄,而非直接进入大纲或起草阶段。
ars/deep-research/WORKFLOW.mdsocratic即使表述中包含论文写作意图,以下情况也视为苏格拉底式触发:
- "I want to write a paper on ..."
- "I have a paper topic/title ..."
- "我想做一篇論文,題目是..."
- "我有一個研究方向/主題,但還不確定問題"
- "幫我想論文題目/收斂研究問題"
此路径下的首次响应:
- 说明由于研究问题尚不明确,请求将被路由至的
deep-research模式。socratic - 依据和
socratic_mentor_agent的指导,提出3-5个苏格拉底式收窄问题。research_question_agent - 在用户确定至少一个候选研究问题(RQ)之前,不要生成大纲、草稿、文献综述或完整流程仪表盘。
仅当用户已有清晰的研究问题、获批的研究框架、数据/结果、文献矩阵、草稿,或明确要求跳过范围界定直接进入大纲/起草阶段时,才直接路由至。仅当用户明确要求完整的研究转论文流程,或表示在苏格拉底式范围界定后继续处理时,才路由至。
ars/academic-paper/WORKFLOW.mdars/academic-pipeline/WORKFLOW.mdClaude-Style Alias Router
Claude风格别名路由
Codex does not install Claude slash commands, but this package emulates their
intent. If the user's request starts with a slash alias () or a plain
alias (), treat it as a mode shortcut, strip the alias token from the
task text, read the matching prompt recipe, then route
to the workflow below.
/ars-planars-planars/commands/ars-*.mdWORKFLOW.mdThe field in command frontmatter is a Claude routing hint only. Codex
uses the current model unless the user explicitly requests another model.
model:| Alias | Read command recipe | Then route to |
|---|---|---|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
If the request body after the alias is a vague topic, tentative title, research
direction, or "題目/主題/方向" without a clear research question, defer to the Paper Topic Scoping Override above before routing to the alias's target mode.
This applies to , , , ,
and .
ars-planars-outlinears-abstractars-lit-reviewars-fullIf the Codex client reserves slash-prefixed input before it reaches the model,
tell the user to use the plain alias form, for example .
ars-plan my topicCodex未安装Claude斜杠命令,但本包模拟其意图。如果用户请求以斜杠别名()或普通别名()开头,则将其视为模式快捷方式,从任务文本中移除别名标记,阅读对应的提示词模板,然后路由至下方的工作流。
/ars-planars-planars/commands/ars-*.mdWORKFLOW.md命令前置元数据中的字段仅为Claude路由提示。Codex使用当前模型,除非用户明确请求其他模型。
model:| 别名 | 阅读命令模板 | 然后路由至 |
|---|---|---|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
如果别名后的请求内容是模糊主题、暂定标题、研究方向或“題目/主題/方向”,且无清晰研究问题,则先遵循上述论文主题范围覆盖规则,再路由至别名的目标模式。此规则适用于、、、和。
ars-planars-outlinears-abstractars-lit-reviewars-full如果Codex客户端在请求到达模型前保留了斜杠前缀输入,请告知用户使用普通别名形式,例如。
ars-plan my topicCodex Runtime Mapping
Codex运行时映射
The upstream ARS files were written for Claude Code. Apply these mappings when
using them in Codex:
| Upstream wording | Codex behavior |
|---|---|
| Agent Team, agent, dispatch, handoff | Read the referenced |
| Agent tool, Task tool, subagent | Do not spawn agents automatically. Only use Codex subagents when the user explicitly asks for delegation or parallel agents. |
| AskUserQuestion | Ask concise clarification questions, or use Codex's structured user-input tool when available in the active mode. |
| WebSearch | Use Codex web browsing for current facts, source verification, citation checks, and external evidence. Provide source links. |
| Bash, Write, Edit | Treat as capability descriptions, not required tool names. Follow Codex safety rules and the user's filesystem constraints. |
| Claude, Claude Code, model-specific wording | Interpret as "the current Codex agent" unless the text is part of a disclosure template or historical example. |
| Treat upstream secondary-model dispatch instructions as no-op unless the user explicitly asks for cross-model review. When explicitly enabled in this Codex package, use Anthropic Claude Opus 4.7 via API ( |
| These are optional upstream bibliographic lookup settings. Use them only when the user explicitly runs contamination-signal migration or programmatic reference verification; normal Codex routing does not require them. |
| Read as "a new Codex conversation". Material Passport reset semantics still apply; only the runtime changes. This rule covers |
| Treat |
SessionStart hook, SubagentStop hook, | Treat as upstream Claude Code hook metadata only. Do not install or execute Claude hooks in Codex unless the user explicitly asks to inspect or port a hook. |
上游ARS文件是为Claude Code编写的。在Codex中使用时,请应用以下映射:
| 上游表述 | Codex行为 |
|---|---|
| Agent Team、agent、dispatch、handoff | 将引用的 |
| Agent tool、Task tool、subagent | 不要自动生成Agent。仅当用户明确请求委托或并行Agent时,才使用Codex子Agent。 |
| AskUserQuestion | 提出简洁的澄清问题,或在当前模式可用时使用Codex的结构化用户输入工具。 |
| WebSearch | 使用Codex网页浏览功能获取当前事实、来源验证、引用检查和外部证据,并提供来源链接。 |
| Bash、Write、Edit | 视为功能描述,而非必需工具名称。遵循Codex安全规则和用户的文件系统限制。 |
| Claude、Claude Code、模型特定表述 | 解释为“当前Codex Agent”,除非文本属于披露模板或历史示例。 |
| 将上游跨模型调度指令视为无操作,除非用户明确请求跨模型评审。当在本Codex包中明确启用时,通过API使用Anthropic Claude Opus 4.7( |
| 这些是可选的上游文献查找设置。仅当用户明确运行污染信号迁移或程序化参考验证时使用;常规Codex路由不需要这些设置。 |
| 解读为“新的Codex对话”。材料通行证重置语义仍然适用;仅运行时改变。此规则覆盖 |
| 将 |
SessionStart hook、SubagentStop hook、 | 仅视为上游Claude Code钩子元数据。除非用户明确要求检查或移植钩子,否则不要在Codex中安装或执行Claude钩子。 |
Agent Prompt Use
Agent提示词使用
When a workflow lists agents:
- Read the workflow to identify the mode and phase.
WORKFLOW.md - Read the specific files for the current phase.
agents/<name>.md - Treat each agent file as a scoped role prompt with an input/output contract.
- Produce the phase output in the current conversation unless the user requested files.
- Use when a phase hands material to another phase.
ars/shared/handoff_schemas.md
For multi-review phases, preserve independence by writing each reviewer section
before synthesizing. Do not let the final synthesis erase critical findings from
devil's advocate or methodology roles.
当工作流列出Agent时:
- 阅读工作流以确定模式和阶段。
WORKFLOW.md - 阅读当前阶段对应的特定文件。
agents/<name>.md - 将每个Agent文件视为具有输入/输出契约的限定角色提示词。
- 在当前对话中生成阶段输出,除非用户请求文件。
- 当一个阶段向另一个阶段移交材料时,使用。
ars/shared/handoff_schemas.md
对于多评审阶段,在合成前保留每个评审部分的独立性。不要让最终合成掩盖来自魔鬼代言人或方法论角色的关键发现。
Canonical Agent Files
标准Agent文件
Use these exact filenames. Do not invent hyphenated alternatives or rename files
from memory.
ars/deep-research/agents/bibliography_agent.mddevils_advocate_agent.mdeditor_in_chief_agent.mdethics_review_agent.mdmeta_analysis_agent.mdmonitoring_agent.mdreport_compiler_agent.mdresearch_architect_agent.mdresearch_question_agent.mdrisk_of_bias_agent.mdsocratic_mentor_agent.mdsource_verification_agent.mdsynthesis_agent.mdars/academic-paper/agents/abstract_bilingual_agent.mdargument_builder_agent.mdcitation_compliance_agent.mddraft_writer_agent.mdformatter_agent.mdintake_agent.mdliterature_strategist_agent.mdpeer_reviewer_agent.mdrevision_coach_agent.mdsocratic_mentor_agent.mdstructure_architect_agent.mdvisualization_agent.mdars/academic-paper-reviewer/agents/devils_advocate_reviewer_agent.mddomain_reviewer_agent.mdeditorial_synthesizer_agent.mdeic_agent.mdfield_analyst_agent.mdmethodology_reviewer_agent.mdperspective_reviewer_agent.mdars/academic-pipeline/agents/claim_ref_alignment_audit_agent.mdcollaboration_depth_agent.mdintegrity_verification_agent.mdpipeline_orchestrator_agent.mdstate_tracker_agent.mdars/experiment-agent/agents/code_runner_agent.mdstudy_manager_agent.md使用以下确切文件名。不要自行发明连字符替代名称或凭记忆重命名文件。
ars/deep-research/agents/bibliography_agent.mddevils_advocate_agent.mdeditor_in_chief_agent.mdethics_review_agent.mdmeta_analysis_agent.mdmonitoring_agent.mdreport_compiler_agent.mdresearch_architect_agent.mdresearch_question_agent.mdrisk_of_bias_agent.mdsocratic_mentor_agent.mdsource_verification_agent.mdsynthesis_agent.mdars/academic-paper/agents/abstract_bilingual_agent.mdargument_builder_agent.mdcitation_compliance_agent.mddraft_writer_agent.mdformatter_agent.mdintake_agent.mdliterature_strategist_agent.mdpeer_reviewer_agent.mdrevision_coach_agent.mdsocratic_mentor_agent.mdstructure_architect_agent.mdvisualization_agent.mdars/academic-paper-reviewer/agents/devils_advocate_reviewer_agent.mddomain_reviewer_agent.mdeditorial_synthesizer_agent.mdeic_agent.mdfield_analyst_agent.mdmethodology_reviewer_agent.mdperspective_reviewer_agent.mdars/academic-pipeline/agents/claim_ref_alignment_audit_agent.mdcollaboration_depth_agent.mdintegrity_verification_agent.mdpipeline_orchestrator_agent.mdstate_tracker_agent.mdars/experiment-agent/agents/code_runner_agent.mdstudy_manager_agent.mdShared Resources
共享资源
Use for cross-workflow contracts and quality gates:
ars/shared/- defines inter-stage artifact schemas.
ars/shared/handoff_schemas.md - defines writing voice calibration.
ars/shared/style_calibration_protocol.md - defines fidelity, balanced, and originality modes.
ars/shared/mode_spectrum.md - defines compliance checks.
ars/shared/agents/compliance_agent.md - ,
ars/shared/compliance_checkpoint_protocol.md, andars/shared/prisma_trAIce_protocol.mddefine integrity and reporting gates.ars/shared/raise_framework.md - contains upstream validators and reference adapters.
ars/scripts/ - contains upstream non-PDF fixtures and templates.
ars/examples/ - contains upstream design specs referenced by ARS protocols.
ars/docs/design/ - contains upstream Claude slash-command prompt recipes.
ars/commands/ - contains upstream Claude hook metadata preserved for traceability.
ars/hooks/ - contains upstream fixture corpora used by validator tests.
ars/tests/
When an ARS file points to , resolve it as .
When it points to another workflow, resolve it under .
When it points to root-level , , or , resolve
it under , , or .
shared/...ars/shared/...ars/<workflow>/...scripts/...examples/...docs/...ars/scripts/...ars/examples/...ars/docs/...使用获取跨工作流契约和质量检查:
ars/shared/- 定义了阶段间工件模式。
ars/shared/handoff_schemas.md - 定义了写作风格校准规则。
ars/shared/style_calibration_protocol.md - 定义了保真度、平衡和原创性模式。
ars/shared/mode_spectrum.md - 定义了合规性检查。
ars/shared/agents/compliance_agent.md - 、
ars/shared/compliance_checkpoint_protocol.md和ars/shared/prisma_trAIce_protocol.md定义了完整性和报告检查。ars/shared/raise_framework.md - 包含上游验证器和参考适配器。
ars/scripts/ - 包含上游非PDF示例和模板。
ars/examples/ - 包含ARS协议引用的上游设计规范。
ars/docs/design/ - 包含上游Claude斜杠命令提示词模板。
ars/commands/ - 包含为可追溯性保留的上游Claude钩子元数据。
ars/hooks/ - 包含验证器测试使用的上游示例语料库。
ars/tests/
当ARS文件指向时,解析为。当指向另一个工作流时,解析为。当指向根目录的、或时,解析为、或。
shared/...ars/shared/...ars/<workflow>/...scripts/...examples/...docs/...ars/scripts/...ars/examples/...ars/docs/...Inactive Upstream Scripts
非活跃上游脚本
manifest.jsoninactive_upstream_scripts.claude/CLAUDE.mdars/scripts/run_codex_audit.shmanifest.jsoninactive_upstream_scripts.claude/CLAUDE.mdars/scripts/run_codex_audit.shVerification Discipline
验证原则
For claims, citations, references, statistics, journal policies, API behavior, and
current facts, verify against primary or authoritative sources. If verification is
not possible, mark the item as unverified instead of inventing support.
Never fabricate references. For citation existence checks, prefer DOI or official
metadata lookup, then authoritative web search. Semantic Scholar, OpenAlex, and
Crossref API instructions are in ; use them only
when the task needs programmatic reference verification.
ars/deep-research/references/对于主张、引用、参考资料、统计数据、期刊政策、API行为和当前事实,需对照原始或权威来源进行验证。如果无法验证,应标记为未验证,而非编造支持依据。
切勿伪造参考资料。对于引用存在性检查,优先使用DOI或官方元数据查找,再进行权威网页搜索。Semantic Scholar、OpenAlex和Crossref API说明位于;仅当任务需要程序化参考验证时才使用。
ars/deep-research/references/Output Defaults
输出默认值
- Default language follows the user's language.
- For Chinese, use Traditional Chinese unless the user requests otherwise.
- For staged workflows, show the current stage, required inputs, output artifact, and whether the next gate is optional or mandatory.
- For paper/research outputs, keep uncertainty explicit and separate evidence, inference, and recommendation.
- 默认语言遵循用户使用的语言。
- 中文默认使用繁体中文,除非用户另有要求。
- 对于阶段性工作流,显示当前阶段、所需输入、输出工件,以及下一检查点是可选还是必填。
- 对于论文/研究输出,明确保留不确定性,区分证据、推断和建议。