dac-workflow
Use to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage abstract-then-manuscript submission on Softconf, the winter review, the March notification, the April camera-ready and copyright for the ACM Digital Library, and the July conference in Long Beach — with the Engineering-Track and Late-Breaking-Results side calendars.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-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.
# DAC Workflow Run the DAC year backward from the deadline. DAC's Research-Manuscript cycle is a **single annual deadline in mid-to-late November** (DAC 2026: manuscript ~19 November 2025) leading to a **July** conference (DAC 2026: Long Beach, California, 26-29 July 2026). Unlike the two-cycle software venues, DAC gives you one archival shot per year, so the calendar is unforgiving. Every date below is a **DAC 2026 snapshot** read on 2026-07-09; reopen the live event pages first (`resources/official-source-map.md`). ## The two-stage submission (do not miss stage one) DAC splits the research submission into **two stages on the Softconf/START system** (`dac26`): - **Stage 1 — Abstract.** Register title, full abstract, and **all co-authors** roughly a week before the manuscript deadline. This stage seeds reviewer assignment and conflict detection; if you skip it, the system will not accept your PDF later. - **Stage 2 — Manuscript.** Upload the anonymized 6+1-page PDF by the manuscript deadline. There is **no grace period** to fix a malformed or non-anonymous PDF after the cutoff. Register with the real title and abstract, not a placeholder — the abstract drives which TPC members bid
- The two-stage submission (do not miss stage one)
- The DAC 2026 research calendar (snapshot — verify each cycle)
- Side calendars (different deadlines — do not conflate)
- Backward plan from the November manuscript deadline
- Between notification and camera-ready
- Standing reminders
- Output format
What does the dac-workflow skill do?
Use to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage abstract-then-manuscript submission on Softconf, the winter review, the March notification, the April camera-ready and copyright for the ACM Digital Library, and the July conference in Long Beach — with the Engineering-Track and Late-Breaking-Results side calendars.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill dac-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.