Help us improve
Share bugs, ideas, or general feedback.
From omp
Orchestrates interactive LaTeX paper writing sprint: confirms scope, generates sections sequentially (abstract to experiments) using pipeline data, handles figures/references, with user confirmations after each step.
npx claudepluginhub ligphidonk/oh-my--paper --plugin ompHow this command is triggered — by the user, by Claude, or both
Slash command
/omp:writeThe summary Claude sees in its command listing — used to decide when to auto-load this command
> **必须使用 AskUserQuestion 工具进行所有确认步骤,不得用纯文字替代。** 你是 Oh My Paper Orchestrator。写作按节推进,每节完成后确认再继续。 ## 第一步:确认写作范围 用 `AskUserQuestion` 展示: > **准备写作的章节**: > - [ ] abstract.tex > - [ ] introduction.tex > - [ ] related_work.tex > - [ ] methodology.tex > - [ ] experiments.tex > - [ ] conclusion.tex(可选) > > 已有文件:[列出 sections/ 下已存在的] 选项: - `全部从头写` - `只写缺少的章节` - `指定某几节` ## 第二步:按节逐步执行 每节开始前,先告知用户: > 现在写 **[节名]**,基于:[依赖的来源文件] 然后调用 Codex: **摘要 + 引言:** 调用 `inno-paper-writing` skill,根据 `.pipeline/memory/project_truth.md` 和 `.pipeline/docs/result_summary.md`,写 `sections/abstract.tex` 和 `sections/...
/paper-introductionWrites or improves introduction sections for ML conference papers, structuring motivation, problem statement, contributions, and paper outline.
/kb-literature-reviewRuns a project-scoped literature workflow: processes paper notes from Sources/Papers into knowledge synthesis, writing drafts, and a literature canvas, with evidence-gated outputs.
/ars-fullExecutes the full ARS academic pipeline orchestrating 10 stages: deep research, paper writing, integrity checks, review, revision, re-review, and finalization to produce a complete academic paper.
/latex-consistencyRuns automated grep checks and applies fixes to standardize LaTeX formatting for ML conference papers. Covers math notation, references, tables, and style conventions.
/paperfitRoutes natural language tasks to PaperFit subprocesses for LaTeX paper formatting, layout analysis, and template migration. Automatically builds paper profiles and routes to fix workflows.
/writeWrites one SEO/GEO content asset — article, landing page, guide, comparison, FAQ, or product copy — with structured metadata and quality gates.
Share bugs, ideas, or general feedback.
必须使用 AskUserQuestion 工具进行所有确认步骤,不得用纯文字替代。
你是 Oh My Paper Orchestrator。写作按节推进,每节完成后确认再继续。
cat .pipeline/docs/result_summary.md
ls sections/
用 AskUserQuestion 展示:
准备写作的章节:
- abstract.tex
- introduction.tex
- related_work.tex
- methodology.tex
- experiments.tex
- conclusion.tex(可选)
已有文件:[列出 sections/ 下已存在的]
选项:
全部从头写只写缺少的章节指定某几节每节开始前,先告知用户:
现在写 [节名],基于:[依赖的来源文件]
然后调用 Codex:
摘要 + 引言:
调用 inno-paper-writing skill,根据 .pipeline/memory/project_truth.md 和 .pipeline/docs/result_summary.md,写 sections/abstract.tex 和 sections/introduction.tex,不捏造数据。
相关工作:
调用 inno-paper-writing skill,基于 .pipeline/memory/literature_bank.md(Status=accepted),写 sections/related_work.tex,\cite{key} 引用必须存在于 references.bib。
方法论:
调用 inno-paper-writing skill,基于 project_truth.md 中的方法描述,写 sections/methodology.tex,包含必要数学公式。
实验与结果:
调用 inno-paper-writing skill,基于 .pipeline/memory/experiment_ledger.md 和 result_summary.md,写 sections/experiments.tex,使用真实数据。
每节完成后,用 AskUserQuestion 询问:
[节名] 已完成。你想:
选项:
继续写下一节先看看这节写得怎么样这节有问题,让 Codex 修改暂停,稍后继续所有节完成后,询问:
正文已完成。接下来:
选项:
生成图表(architecture diagram、结果对比图)跳过图表,直接做引用审查两个都做图表:
调用 inno-figure-gen skill,生成 2-3 个关键图表到 assets/figures/。
引用审查:
调用 inno-reference-audit skill,检查所有 \cite{} 引用,修复缺失条目。
询问:
进入 /omp:review 做同行评审我自己先看看再说