icalp-workflow
Use when planning an ICALP (EATCS) campaign backward from its single annual February deadline, through abstract registration, the anonymous submission, the Track B rebuttal window, the April notification, and the LIPIcs camera-ready and presentation, and when coordinating a full-version (arXiv/ECCC) release alongside the anonymous submission.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-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.
# ICALP Workflow Run the ICALP year backward from the **single annual February deadline**. ICALP posts one research-paper deadline per year across its two tracks, so unlike a multi-deadline venue there is no "next cycle in a few months" — a missed February means a full year lost. The calendar below is the ICALP 2026 (53rd, Royal Holloway) cycle, verified 2026-07-09; reopen the live Important Dates page and the correct track's HotCRP deadline before trusting any date. ## The one-cycle calendar (ICALP 2026 anchor) ```text [early February] Abstract registration (2026: 3 Feb, AoE) — title/abstract/authors/conflicts [~3 days later] Full submission (2026: 6 Feb, AoE) — anonymized 15-page PDF + appendix [late March] Track B rebuttal (2026: 21-24 Mar) — Track B only; Track A no general rebuttal [late April] Notification (2026: 20 Apr) [spring] Camera-ready in LIPIcs (lipics-v2021); exact date 待核实 per cycle [July] Conference (2026: 7-10 Jul, workshops 6 Jul), Royal Holloway ``` ## Backward plan from the February deadline - **T-12 to T-8 weeks:** prove the theorems. ICALP results are proofs, and a proof is not "almost done" until it is written in full — budget for the gap between "I believe
- The one-cycle calendar (ICALP 2026 anchor)
- Backward plan from the February deadline
- The Track B rebuttal (know if it applies to you)
- Coordinating the full version
- After notification
- Milestone checklist
- Output format
What does the icalp-workflow skill do?
Use when planning an ICALP (EATCS) campaign backward from its single annual February deadline, through abstract registration, the anonymous submission, the Track B rebuttal window, the April notification, and the LIPIcs camera-ready and presentation, and when coordinating a full-version (arXiv/ECCC) release alongside the anonymous submission.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-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.