conext-workflow
Use when planning an ACM CoNEXT campaign backward from a deadline, covering the choice between the December and June submission cycles, the mandatory registration step, the one-shot major-revision window, the reproducibility badge opt-in due at submission, PACMNET camera-ready, and presentation — all on CoNEXT's distinctive two-cycles-per-year calendar.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CoNEXT Workflow Plan the whole campaign backward from the cutoff. CoNEXT's defining feature is **two submission cycles a year** — a **December** deadline and a **June** deadline — both feeding one annual program and one rolling PACMNET volume. The first decision is therefore not "when do I write?" but "which cycle am I targeting, and is my evidence ready for it?" Every date below is the CoNEXT 2026 snapshot read on 2026-07-09 (see [`../../resources/official-source-map.md`](../../resources/official-source-map.md)); reopen the live Important Dates page before committing. ## Choose the cycle ```text [December cycle] register 5 Dec 2025 -> submit 12 Dec 2025 -> early-reject Feb 2026 -> notify 31 Mar 2026 -> camera-ready 30 Apr 2026 -> June 2026 PACMNET issue (major revision path) revision due 29 May 2026 -> resubmit 5 Jun 2026 -> camera-ready 31 Jul 2026 [June cycle] submit 5 Jun 2026 -> (its own review round, notification, and later PACMNET issue) ``` - Target the **nearer honest deadline** your evidence is actually ready for. A half-finished testbed campaign rushed into December scores worse than a complete one in June. - If you earn a one-shot major revision in the December cycle,
- Choose the cycle
- Backward plan from a chosen cutoff (T = submission day)
- After submission
- Roles and hand-offs
- Calendar hygiene
- Output format
What does the conext-workflow skill do?
Use when planning an ACM CoNEXT campaign backward from a deadline, covering the choice between the December and June submission cycles, the mandatory registration step, the one-shot major-revision window, the reproducibility badge opt-in due at submission, PACMNET camera-ready, and presentation — all on CoNEXT's distinctive two-cycles-per-year calendar.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.