asplos-workflow
Use when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21 notification, Major Revision resubmission six weeks later, artifact evaluation, and the April 2027 conference in Crete, with owners per risk.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-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.
# ASPLOS Workflow An ASPLOS campaign is a pipeline with two entry gates per edition and a revision side-channel, not a single deadline sprint. All dates below are the verified 2027 cycle (CFP and conference site, checked 2026-07-08); reopen the official pages before committing a team to any of them. ## The 2027 cycle as a calendar | Gate | April cycle | September cycle | |---|---|---| | Full-paper deadline (11:59 PM AoE) | April 15, 2026 — **passed** | **September 9, 2026 — the live gate** | | Author response | July 6-9, 2026 — **open this week** (as of 2026-07-08) | December 1-4, 2026 | | Notification | July 27, 2026 | December 21, 2026 | | Major Revision due | camera-ready deadline, 6 weeks after notification | camera-ready deadline, 6 weeks after notification | | Conference | April 11-15, 2027, Heraklion, Crete, Greece | same | There is no separate abstract deadline in 2027, and no mid-year third round — the edition moved from three deadlines to two. Missing September means waiting for the next edition's first gate. ## Working backward from September 9, 2026 A credible countdown for a systems paper with hardware-dependent evidence: ```text T-10 weeks (by ~Jul 1) Freeze the claim
- The 2027 cycle as a calendar
- Working backward from September 9, 2026
- Role assignments that prevent known failures
- Branch planning at notification (December 21, 2026)
- Cross-edition cautions
- Hardware lead times are schedule items
- Between notification and Crete
- Pipelining across gates
- Output format
What does the asplos-workflow skill do?
Use when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21 notification, Major Revision resubmission six weeks later, artifact evaluation, and the April 2027 conference in Crete, with owners per risk.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-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.