oopsla-workflow
Use when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or OOPSLA2 PACMPL issue, scheduling artifact evaluation, and landing the SPLASH talk, with dates re-anchored to the live cycle.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-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.
# OOPSLA Workflow OOPSLA gives a paper *two doors per year* into the same PACMPL volume — for 2026, October 10, 2025 (Round 1 → Issue OOPSLA1, published from April 1, 2026) and March 17, 2026 (Round 2 → Issue OOPSLA2, from October 1, 2026), with all outcomes presented at SPLASH (Oakland, October 4–9, 2026; OOPSLA talks October 5–7). Planning an OOPSLA campaign is therefore a routing problem over rounds and revision outcomes, not a countdown to a single deadline. As of 2026-07-08 the next open door is the 2027 volume's Round 1, CFP not yet posted (待核实) — re-anchor every date below to live pages. ## Door choice: October vs March | Factor | Favors the October round | Favors the March round | | --- | --- | --- | | Revision insurance | Major Revision lands in March, **same volume** | Major Revision waits ~7 months for next volume's R1 | | Publication timing | April issue; citable before the conference | October issue; publishes near conference time | | Evidence maturity | Requires the evaluation done by early fall | Buys a winter of experiments | | Team calendar | Summer build, fall write | Fall build, winter write | | Talk lead time | Long runway to SPLASH | Acceptance close to travel
- Door choice: October vs March
- Campaign state machine
- Backward plan from a target round (T = deadline)
- Revision-path budgeting
- Post-acceptance rail
- Output format
What does the oopsla-workflow skill do?
Use when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or OOPSLA2 PACMPL issue, scheduling artifact evaluation, and landing the SPLASH talk, with dates re-anchored to the live cycle.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-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.