osdi-workflow
Use when planning or managing a full OSDI cycle — the December title-registration and submission deadlines on HotCRP, the silent no-rebuttal review window, March notification, the May artifact deadline, June shepherded final papers, and the July conference — including rejection retargeting to SOSP or NSDI.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-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.
# OSDI Workflow Project-manage the OSDI year. All dates below are the verified OSDI '26 pipeline (read 2026-07-08) and are one cycle's snapshot; the '27 CFP was not yet posted at check time (待核实), so anchor the next cycle only after `usenix.org/conference/osdi27` publishes its dates. ## The 2026 pipeline, with what each date actually demanded | Date (2026 cycle) | Gate | What must be true by then | |---|---|---| | Dec 4, 2025, 2:59 pm PST | Title/abstract registration (both tracks) | Title, abstract, authors, track choice on HotCRP | | Dec 11, 2025, 2:59 pm PST | Full submission | Final anonymized 12-page PDF uploaded | | Mar 26, 2026 | Notification | Decision: accept / conditional accept / reject | | May 8, 2026, 8:59 pm PDT | Artifact submission | Archive + AE README ready (accepted papers) | | Jun 9, 2026 | Final papers | Shepherd-approved 14-page PDF in the system | | Jul 13–15, 2026 | Conference (Seattle) | Presenter registered and prepared | Three structural notes that surprise newcomers: - **The deadlines are Pacific clock time, not AoE.** 2:59 pm PST is late-night only in Europe; in East Asia it is early morning the next day. Compute your local cutoff explicitly and pin it
- The 2026 pipeline, with what each date actually demanded
- Backward plan from December
- The silent window (December → March)
- Notification branches (March 26)
- The retargeting calendar
- Failure modes this skill exists to prevent
- Multi-paper coordination
- Output format
What does the osdi-workflow skill do?
Use when planning or managing a full OSDI cycle — the December title-registration and submission deadlines on HotCRP, the silent no-rebuttal review window, March notification, the May artifact deadline, June shepherded final papers, and the July conference — including rejection retargeting to SOSP or NSDI.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-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.