plan-submission

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Plan Submission

提交规划

Turn "the deadline is in N weeks" into a dated, phase-aware milestone plan. Works backwards from the paper deadline (or forwards through rebuttal and camera-ready if the deadline already passed), anchored to a

venues/conferences/<venue>-<year>.yml

profile. Companion skills:

parse-cfp

(creates the profile),

preflight-check

(the T-3d desk-reject lint),

write-rebuttal

prepare-camera-ready

将“截止日期还有N周”转化为带日期、感知阶段的里程碑计划。从论文截止日期倒推（若截止日期已过，则顺推反驳期和终稿阶段），以

venues/conferences/<venue>-<year>.yml

配置文件为依据。配套技能：

parse-cfp

（创建配置文件）、

preflight-check

（提交前3天的初审检查）、

write-rebuttal

、

prepare-camera-ready

。

When to use

使用场景

"Plan my SIGSPATIAL submission" / "what do I need to do before the deadline?"
"How many days until the NeurIPS deadline?" (AoE confusion included)
"When do I have to register the abstract?" / "when does the rebuttal start?"
The user just picked a venue (via
```
select-venue
```
) and asks "what now?"

“帮我规划SIGSPATIAL的提交” / “截止前我需要做什么？”
“NeurIPS的截止日期还有多少天？”（包含AoE时区混淆问题）
“摘要注册的截止时间是什么时候？” / “反驳期什么时候开始？”
用户刚选定会议（通过
```
select-venue
```
）并询问“接下来该做什么？”

Inputs

输入信息

A venue + year (and ideally a track). The profile must exist at
```
venues/conferences/<venue>-<year>.yml
```
; if it does not, run
```
parse-cfp
```
first — never plan from remembered dates.
Today's date, and any user-specific constraints (vacations, co-author availability, experiments still running).
```
CONTACT_EMAIL
```
env var if the live re-verification fetch is used.

会议名称+年份（最好包含赛道）。配置文件必须存在于
```
venues/conferences/<venue>-<year>.yml
```
；若不存在，需先运行
```
parse-cfp
```
——绝不依靠记忆的日期进行规划。
当前日期，以及用户的特定约束条件（休假时间、合作者可用时间、仍在进行的实验）。
若使用实时重新验证功能，需提供
```
CONTACT_EMAIL
```
环境变量。

Process

流程步骤

Resolve the venue profile. Locate
```
venues/conferences/<venue>-<year>.yml
```
. Missing or from a previous cycle → route through
```
parse-cfp
```
to create/refresh it before planning. Check the profile's
```
verified:
```
block — if
```
confidence
```
is not
```
verified-live
```
or
```
verified.date
```
is old, treat every date as suspect.
Re-verify the critical dates against the live CFP. Mandatory before the user relies on the plan. Run:
```
python3 scripts/fetch_page.py "<cfp_url from the profile>"
```
Confirm the abstract deadline, paper deadline, and timezone on the live page (deadlines slip mid-cycle — extensions are common, but so are silent corrections). On mismatch, update the profile first. If the page is JS-rendered or down, say so and mark the plan "dates unverified".
Build the timeline. Run:
```
python3 scripts/build_timeline.py venues/conferences/<venue>-<year>.yml \
    --track "<track>" --today YYYY-MM-DD
```
The script is offline and deterministic: it detects the current phase (pre-submission / under-review / camera-ready), computes days remaining for every profile deadline, and emits dated milestones with standard backwards offsets (T-21d dual-submission audit and reciprocal-reviewing check, T-14d system accounts, T-10d author-list freeze, abstract registration at its real date, T-5d supplementary, T-3d preflight, T-2d draft upload, T-1d final upload).
```
--camera-ready YYYY-MM-DD
```
supplies a deadline the profile lists as null.
```
--format json
```
for machine use.
Customize the milestones using references/milestone-playbook.md: what each milestone actually requires, why the offset is what it is, supplementary/code size limits, reciprocal-reviewing mechanics, and the AoE math. Adjust offsets for the user's constraints (e.g. co-author on leave at T-10d → freeze the author list earlier). Never move a HARD deadline; only prep milestones are adjustable.
Add per-system steps from references/submission-systems.md for the profile's
```
review.submission_system
```
— account lead times (OpenReview profile moderation can take ~2 weeks), what the submission form demands, conflict-of-interest entry, and each system's signature gotcha (HotCRP's "ready for review" checkbox, PCS metadata lock, EasyChair co-author email typos, CMT COI lists).
Run the dual-submission audit interactively. Quote the profile's
```
review.dual_submission
```
policy verbatim, then ask the user to inventory every overlapping manuscript by ANY co-author that is under review or planned elsewhere (including workshop versions and arXiv plans). Flag conflicts against the quoted policy; when the policy is ambiguous, say so and point at the CFP — do not adjudicate.
Present the plan: phase, key-dates table with days remaining, milestone table (OVERDUE items first, called out explicitly), per-system steps, policy gates, and the re-verify warning. If the paper deadline has already passed, do NOT pretend otherwise — plan the next phase and say plainly which deadlines are gone.

解析会议配置文件。找到
```
venues/conferences/<venue>-<year>.yml
```
文件。若文件缺失或属于上一周期，需先通过
```
parse-cfp
```
创建/更新配置文件再进行规划。检查配置文件的
```
verified:
```
块——若
```
confidence
```
不是
```
verified-live
```
或
```
verified.date
```
已过期，则所有日期均需标记为可疑。
对照实时CFP重新验证关键日期。用户依赖计划前必须执行此步骤。运行：
```
python3 scripts/fetch_page.py "<配置文件中的cfp_url>"
```
确认实时页面上的摘要截止日期、论文截止日期及时区（周期内截止日期可能变动——延期很常见，无声修正也时有发生）。若存在不一致，需先更新配置文件。若页面为JS渲染或无法访问，需告知用户并标记计划“日期未验证”。
构建时间线。运行：
```
python3 scripts/build_timeline.py venues/conferences/<venue>-<year>.yml \
    --track "<赛道>" --today YYYY-MM-DD
```
该脚本为离线且确定性工具：它会检测当前阶段（提交前/审核中/终稿阶段），计算配置文件中每个截止日期的剩余天数，并生成带日期的里程碑，包含标准逆向时间差（提前21天完成双重提交审核与互评检查、提前14天准备系统账户、提前10天冻结作者名单、摘要注册按实际日期、提前5天准备补充材料、提前3天进行初审检查、提前2天上传草稿、提前1天完成最终上传）。
```
--camera-ready YYYY-MM-DD
```
可用于补充配置文件中标记为null的终稿截止日期。
```
--format json
```
可生成供机器使用的格式。
参考references/milestone-playbook.md自定义里程碑：明确每个里程碑的实际要求、时间差设定的原因、补充材料/代码大小限制、互评机制以及AoE时区计算方式。根据用户的约束条件调整时间差（例如，合作者在提前10天休假→提前冻结作者名单）。绝不修改硬性截止日期；仅可调整准备阶段的里程碑时间。
根据配置文件中的
review.submission_system
，添加references/submission-systems.md中的各系统操作步骤——账户准备周期（OpenReview资料审核可能需要约2周）、提交表单要求、利益冲突填写，以及各系统的注意事项（HotCRP的“准备好审核”复选框、PCS元数据锁定、EasyChair合作者邮箱拼写错误、CMT利益冲突列表）。
交互式执行双重提交审核。逐字引用配置文件中的
```
review.dual_submission
```
政策，然后要求用户列出所有合作者正在其他地方审核或计划提交的重叠稿件（包括研讨会版本和arXiv计划）。对照引用的政策标记冲突；若政策表述模糊，需告知用户并指向CFP——不得自行裁决。
展示计划：当前阶段、带剩余天数的关键日期表、里程碑表（逾期项优先，明确标注）、各系统操作步骤、政策要求，以及重新验证提示。若论文截止日期已过，不得隐瞒——规划下一阶段并明确告知哪些截止日期已过期。

Output

输出结果

A dated submission plan in Markdown: current phase, key dates with days-remaining (timezone noted), backwards milestone schedule with status (in Nd / TODAY / OVERDUE / PASSED), submission-system checklist, policy gates (dual submission, LLM policy, reciprocal reviewing), and the closing notice: "Dates from
<profile>
(verified
<date>
). Re-verified against
<cfp_url>
on
<today>
. Deadlines change mid-cycle — check the CFP again before each milestone."

带日期的Markdown格式提交计划：当前阶段、带剩余天数的关键日期（标注时区）、逆向里程碑时间表（状态包括：剩余N天/今日/逾期/已完成）、提交系统检查清单、政策要求（双重提交、LLM政策、互评），以及结尾提示：“日期来自
<配置文件>
（验证于
<日期>
）。于
<今日>
对照
<cfp_url>
重新验证。周期内截止日期可能变动——每个里程碑前请再次检查CFP。”

Guardrails

约束规则

Never invent a date. A
```
null
```
in the profile stays unknown in the plan, with an instruction on where to find it — a guessed deadline is worse than none.
Always state the timezone next to every deadline. AoE is common, not universal (SIGSPATIAL uses Pacific Time); a wrong assumption costs a day.
Never submit, register, create accounts, or click anything in any submission system on the user's behalf. The plan tells the user what to do; the user does it.
Past deadlines are reported as passed, never silently dropped or rescheduled.
One page per fetch-script invocation; cache stays under
```
.cache/
```
(gitignored); never commit fetched CFP text.

绝不编造日期。配置文件中的
```
null
```
值需保留为未知，并告知用户查找途径——猜测的截止日期比没有更糟。
每个截止日期旁必须标注时区。AoE时区很常见，但并非通用（SIGSPATIAL使用太平洋时间）；错误的假设可能导致损失一天时间。
绝不代表用户在任何提交系统中进行提交、注册、创建账户或点击操作。计划仅告知用户需执行的操作；由用户自行完成。
已过期的截止日期需标记为已完成，不得默默删除或重新安排。
每次调用抓取脚本仅获取一页内容；缓存存储在
```
.cache/
```
（已加入git忽略）；绝不提交抓取的CFP文本。

Bundled files

捆绑文件

references/milestone-playbook.md — what every milestone requires, default offsets and their rationale, supplementary/code limits, reciprocal reviewing, dual-submission audit, AoE math.
references/submission-systems.md — per-system walkthroughs: OpenReview, CMT, EasyChair, HotCRP, PCS.
```
scripts/build_timeline.py
```
— deterministic phase-aware timeline builder (run it; do not compute date arithmetic by hand).
```
scripts/fetch_page.py
```
— polite single-page fetcher for live CFP re-verification (vendored from
```
parse-cfp
```
so this skill is self-contained).
```
scripts/venue_profile.py
```
— shared profile loader (YAML-subset parser + family merge), vendored for self-containment.

references/milestone-playbook.md——每个里程碑的要求、默认时间差及依据、补充材料/代码限制、互评机制、双重提交审核、AoE时区计算方式。
references/submission-systems.md——各系统操作指南：OpenReview、CMT、EasyChair、HotCRP、PCS。
```
scripts/build_timeline.py
```
——确定性阶段感知时间线构建工具（请运行脚本；勿手动计算日期）。
```
scripts/fetch_page.py
```
——用于实时CFP重新验证的礼貌单页抓取工具（从
```
parse-cfp
```
引入，使本技能具备独立性）。
```
scripts/venue_profile.py
```
——共享配置文件加载器（YAML子集解析器 + 家族合并），引入后使本技能具备独立性。