Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/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.
Passed 19 of 21 test cases with the skill, and 6 of 21 without it.
and 23 more in the full report
15 fixed5 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
When setting up calendar holds for an author response (rebuttal) period for a September cycle ASPLOS paper, which specific dates must be blocked on author calendars?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies December 1-4, 2026 for the author response window. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
| 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.
A credible countdown for a systems paper with hardware-dependent evidence:
T-10 weeks (by ~Jul 1) Freeze the claim list; run asplos-topic-selection;
choose evidence instruments (silicon / FPGA / simulator).
T-8 weeks Evaluation infrastructure done: baselines building,
workloads chosen, simulator configs pinned.
T-6 weeks First full results sweep; kill or descope claims the
data will not carry. Start the two-page draft NOW —
it is the part rapid review actually reads.
T-4 weeks Full draft; internal red-team against the rapid-review
question set; ablations running.
T-2 weeks Freeze experiments. Citation-format pass (full names,
no "et al.", DOIs). Anonymity sweep.
T-1 week HotCRP entry created; PDF uploaded; co-author sign-off.
T-0 Sep 9, 11:59 PM AoE HotCRP status shows *complete*, not draft.
test cases passed, vs 6 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.