academic-research-suite

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: academic-research-suite
description: >
  ARS-Codex workflows for research, academic writing, manuscript review,
  research-to-paper pipelines, and experiment planning. Use when the user asks for deep research, literature
  review, systematic review, meta-analysis, research question refinement,
  academic paper drafting, paper revision, citation or integrity checks,
  reviewer simulation, peer review, editorial decision letters, research-to-paper
  workflows, experiment execution planning, statistical interpretation, or human
  study protocol support. Korean triggers: 논문 심사, 논문 수정, 초록 작성,
  체계적 문헌고찰, 연구부터 논문까지. Also use for Claude-style ARS command aliases such as
  /ars-plan, ars-plan, /ars-outline, /ars-abstract, /ars-lit-review,
  /ars-citation-check, /ars-disclosure, /ars-format-convert, /ars-3w,
  /ars-revision-coach, /ars-revision, /ars-reviewer, /ars-mark-read,
  /ars-unmark-read, /ars-cache-invalidate, /ars-rebuttal-audit, and /ars-full. This skill vendors ARS role prompts,
  references, templates, and shared handoff schemas under ars/.
metadata:
  version: "0.1.24"
  upstream_suite: "academic-research-skills"
  codex_adapter: true
allowed-tools: Read, Glob, Grep, WebSearch, Bash(uv *), Bash(python *), Bash(python3 *)
---

# ARS-Codex

This is a Codex adapter for the ARS suite. The vendored ARS content lives under
`ars/`; keep it as source material and route through this file first.

## Versioning

This Codex package is version `0.1.24`. The repo-root `VERSION`, this
`SKILL.md` metadata version, and `manifest.json` `adapter_version` must match.
Vendored ARS suite versions are tracked separately by source repository commit
in `manifest.json`.

## First Rule

Do not load the whole suite by default. Select one workflow, read that workflow's
`WORKFLOW.md`, then load only the agent, reference, template, or shared files needed
for the user's current stage.

The internal workflow entry files are named `WORKFLOW.md`, not `SKILL.md`, so
Codex registers only this root router skill instead of exposing every vendored
upstream workflow as a separate skill.

## Workflow Router

Choose the workflow by intent:

| User intent | Read first |
|---|---|
| Deep research, literature review, systematic review, meta-analysis, fact-checking, research question refinement | `ars/deep-research/WORKFLOW.md` |
| Academic paper writing, paper outline, abstract, revision, citation formatting, AI disclosure, LaTeX/DOCX/PDF formatting guidance | `ars/academic-paper/WORKFLOW.md` |
| Paper review, peer review simulation, editorial decision, reviewer calibration, re-review after revision | `ars/academic-paper-reviewer/WORKFLOW.md` |
| End-to-end research-to-paper pipeline, integrity gate, staged review/revision/finalization workflow | `ars/academic-pipeline/WORKFLOW.md` |
| Experiment planning, code experiment execution plan, human study protocol, statistical interpretation, reproducibility validation | `ars/experiment-agent/WORKFLOW.md` |

If the request spans multiple workflows, start with `ars/academic-pipeline/WORKFLOW.md`
unless the user clearly asked for a single phase.

### Paper 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 `ars-*` alias.

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 `ars/deep-research/WORKFLOW.md` in
`socratic` mode first. This matches the upstream ARS experience where vague
paper-topic requests start with SCR/Socratic narrowing instead of immediate
outline or drafting.

Treat 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 ...