ASPLOS Skills
A 12-skill depth pack for ASPLOS submissions: cross-layer venue fit, the two-deadline HotCRP cycle, rapid review and rebuttal strategy, Major Revision handling, camera-ready, ACM artifact badges, hardware-evaluation reproducibility, supplementary appendices, writing style, related work, experiments, and workflow. Grounded in the official ASPLOS 2027 CFP, HotCRP deadline pages, artifact-evaluation
Skills in this plugin
12- ▌ Asplos Workflow · brycewang-stanfordUse 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.
- ▌ Asplos Submission · brycewang-stanfordUse when running the final pre-upload audit of an ASPLOS submission — the 11-page limit covering figures/tables/footnotes with references excluded, the mandatory template, the no-"et al." full-name citation rule, hyperlinked DOIs, double-blind hygiene, GenAI disclosure, appendix self-containment, and HotCRP completion before the AoE deadline.
- ▌ Asplos Experiments · brycewang-stanfordUse when designing or auditing the evaluation of an ASPLOS paper — choosing among real silicon, FPGA prototypes, and simulators with cycle-accuracy caveats stated, selecting workload suites and baselines that hold up across three communities, attributing wins via ablation, and reporting energy, area, and overhead honestly.
- ▌ Asplos Camera Ready · brycewang-stanfordUse when converting an ASPLOS acceptance or Major Revision decision into a publishable ACM paper within the six-week window — de-anonymization, ACM rights and template obligations, the revision change note, artifact-appendix integration and badge placement, and Digital Library metadata checks.
- ▌ Asplos Related Work · brycewang-stanfordUse when positioning an ASPLOS submission against three communities' literatures at once — covering the architecture, OS/systems, and PL/compiler lanes plus accelerator and prior-ASPLOS lines, handling own-work and arXiv material under the 2027 double-blind rules, and meeting the full-name/DOI citation format.
- ▌ Asplos Supplementary · brycewang-stanfordUse when deciding what goes into an ASPLOS submission's appendices versus the 11 self-contained pages — applying the rule that reviewers are neither required nor encouraged to read supplemental material, using anonymized supplements for unciteable own work, and staging content for the revision and artifact phases.
- ▌ Asplos Writing Style · brycewang-stanfordUse when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and footnotes.
- ▌ Asplos Review Process · brycewang-stanfordUse when reasoning about how an ASPLOS submission will be judged — the two-page rapid-review screen and what it filters, full double-blind review, the author-response window, the Accept / Major Revision / Reject outcome set, how revisions are re-reviewed as submissions, and where authors actually hold leverage in each stage.
- ▌ Asplos Author Response · brycewang-stanfordUse when drafting an ASPLOS author response inside the short fixed window — triaging reviews into factual errors versus questions versus disagreements, budgeting for the ~800 words reviewers are expected to read, arguing only from evidence already in the submission, and positioning the paper for the Accept / Major Revision / Reject decision.
- ▌ Asplos Reproducibility · brycewang-stanfordUse when hardening an ASPLOS paper's results for independent repetition — pinning simulator versions and configs, recording kernel/firmware/BIOS state, packaging FPGA bitstreams and RTL, documenting hardware dependencies an evaluator may lack, and writing availability statements that match what the ACM badges will later require.
- ▌ Asplos Topic Selection · brycewang-stanfordUse when deciding whether a project belongs at ASPLOS or at a single-community venue — applying the cross-layer deletion test, matching against ASPLOS's architecture/PL/OS intersection identity, routing to ISCA/MICRO/HPCA, PLDI/POPL, SOSP/OSDI/EuroSys, SC, or MLSys instead, and choosing between the April and September deadlines.
- ▌ Asplos Artifact Evaluation · brycewang-stanfordUse when preparing an ASPLOS artifact for the post-acceptance evaluation committee — writing the ae.tex Artifact Appendix with software/hardware/dataset dependencies, targeting the Available / Functional / Reproducible badges, archiving on a public repository, and planning the collaborative back-and-forth with evaluators.