podc-workflow
Use when planning an ACM PODC campaign end to end — running the single annual cycle backward from the February deadline through abstract registration, lightweight double-blind review, the late-April notification, the May camera-ready, and the arXiv full version — and coordinating the regular-paper-vs-Brief-Announcement decision along the way.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-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.
# PODC Workflow Plan the year backward from the deadline. PODC runs a **single annual cycle** with a straightforward accept/reject decision and **no journal-style revision round**, so unlike a multi-cycle or major-revision venue, you get one shot per year — the leverage is all in what you submit, not in a second read. Dates below are the PODC 2026 cycle (read 2026-07-09 via renderings; see `resources/official-source-map.md`); reopen the live Important Dates page each year. ## The PODC 2026 calendar (one cycle) | Milestone | Date (23:59 AoE) | What it gates | |---|---|---| | Abstract registration | **11 February 2026** | Title/abstract/authors/conflicts locked; no PDF accepted later without it | | Full-paper submission | **16 February 2026** | The anonymized PDF (regular or Brief Announcement) | | Notification | **29 April 2026** | Accept / reject | | Camera-ready | **20 May 2026** | Final ACM proceedings PDF + rights forms | | Conference | **6-10 July 2026** | In-person presentation at Royal Holloway, University of London | ## Running the year backward ```text [Jul 2026] present in person at Royal Holloway (co-located with SPAA); a paid registration by one author is required [May 2
- The PODC 2026 calendar (one cycle)
- Running the year backward
- Where the leverage is (and is not)
- Coordinating the co-located venues
- The full-version / arXiv track (parallel to the whole cycle)
- Common calendar mistakes
- Output format
What does the podc-workflow skill do?
Use when planning an ACM PODC campaign end to end — running the single annual cycle backward from the February deadline through abstract registration, lightweight double-blind review, the late-April notification, the May camera-ready, and the arXiv full version — and coordinating the regular-paper-vs-Brief-Announcement decision along the way.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-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.