ieeesp-workflow
Use when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows, Revise resubmission timing, the one-year embargo clock, and choosing which cycle a project can realistically hit.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-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.
# IEEE S&P Workflow Use this to run a project against S&P's calendar. Unlike single-deadline ML venues, each S&P symposium accepts papers through **multiple submission cycles**, each a self-contained mini-conference with its own HotCRP site, registration freeze, review rounds, and decision date. Planning means choosing a cycle, not "the deadline." ## The S&P 2027 cycle map (checked 2026-07-08, all dates 待核实 before use) | Milestone | Cycle 1 | Cycle 2 | |---|---|---| | Abstract registration (title/abstract/authors/ORCIDs frozen) | Jun 5, 2026, 7:59:59 AM EDT | Nov 10, 2026 | | Full paper due | Jun 12, 2026 | Nov 17, 2026 | | Early-reject notification | 待核实 | Jan 18, 2027 | | Reviews released to surviving papers | 待核实 | Feb 11, 2027 | | Rebuttal due | 待核实 | Feb 16, 2027 | | Decision (Accept / Revise / Reject) | 待核实 | Mar 5, 2027 | | Symposium (Montreal, Canada) | May 2027 | May 2027 | Two planning facts bite hardest. First, **Cycle 1 for 2027 closed on June 12, 2026** — as of this pack's check date the open path is Cycle 2. Second, S&P states deadlines in a fixed clock time (7:59:59 AM EDT for Cycle 1), **not AoE**; a team assuming Anywhere-on-Earth loses most of a day. ## Registrati
- The S&P 2027 cycle map (checked 2026-07-08, all dates 待核实 before use)
- Registration week is the real deadline
- Backward schedule from a cycle
- Branch plans for the three outcomes
- Choosing between cycles
- Standing risks to assign owners
- Output format
What does the ieeesp-workflow skill do?
Use when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows, Revise resubmission timing, the one-year embargo clock, and choosing which cycle a project can realistically hit.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-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.