itcs-workflow
Use to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the LIPIcs camera-ready, and the January conference with its Graduating Bits session.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-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.
# ITCS Workflow ITCS runs on **one annual cycle** with a distinctive rhythm: submit in **early September**, get a **yes/no in November with no rebuttal in between**, and present the following **January**, with open-access publication in **LIPIcs**. There is no second round, no revise-and-resubmit, and no author-response phase, so the leverage is almost entirely *before* the deadline. Plan the year backward from that September date. Every date below is the **ITCS 2026 snapshot** (Bocconi, Milan); reopen the current call — see [`../../resources/official-source-map.md`](../../resources/official-source-map.md). ## The single-cycle calendar (ITCS 2026 anchor) | Phase | ITCS 2026 date | What actually happens | |---|---|---| | Abstract / registration | **4 Sep 2025** (7:59:59 PM EDT) | Title, abstract, authors, conflicts locked in HotCRP; the abstract drives PC bidding | | Full-paper submission | **6 Sep 2025** (7:59:59 PM EDT) | Anonymized PDF with complete proofs uploaded | | Reviewing (no rebuttal) | Sep-Oct 2025 | PC + external reviewers read; **no author-response phase** | | Notification | **~10 Nov 2025** | Accept / reject; there is no Major Revision category | | Camera-ready | Late
- The single-cycle calendar (ITCS 2026 anchor)
- Working backward from the deadline
- The no-rebuttal consequence, planned for
- After notification
- The Graduating Bits and community layer
- Reverify each cycle
- Output format
What does the itcs-workflow skill do?
Use to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the LIPIcs camera-ready, and the January conference with its Graduating Bits session.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-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.