MICRO Skills
A 12-skill depth pack for MICRO (IEEE/ACM International Symposium on Microarchitecture) submissions: venue fit, HotCRP submission audits, rebuttal/revision strategy, camera-ready, artifact evaluation and ACM badges, simulator-grade reproducibility, the no-appendix page discipline, review process, writing style, related work, experiments, and the four-venue architecture calendar. Grounded in the MI
Skills in this plugin
12- ▌ Micro Workflow · brycewang-stanfordUse when planning a MICRO campaign end to end — the April-to-Athens 2026 cycle clock, the four-venue architecture calendar (MICRO/ISCA/HPCA/ASPLOS) seen from MICRO's October seat, resubmission lattices after each outcome, and starting the MICRO 2027 evaluation stack early enough to matter.
- ▌ Micro Submission · brycewang-stanfordUse when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the abstract-registration gate a week before the paper, minimum 9pt fonts, mandatory page numbers, all-author reference entries, and MICRO's visual-plus-automated format inspection.
- ▌ Micro Experiments · brycewang-stanfordUse when designing or auditing the evaluation of a MICRO paper — choosing the right instrument on the ladder from analytical model to cycle-level simulator to RTL to silicon, tuning baselines the PC will respect, selecting workload suites, running ablations and sensitivity sweeps, and reporting geomeans with full overhead accounting.
- ▌ Micro Camera Ready · brycewang-stanfordUse when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration, keeping the all-author reference rule, integrating rebuttal promises, the optional post-AE artifact appendix, and IEEE/ACM publication logistics.
- ▌ Micro Related Work · brycewang-stanfordUse when building a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating by mechanism structure and cost rather than by numbers, obeying MICRO's all-author citation format, and verifying venue attribution via dblp before citing.
- ▌ Micro Supplementary · brycewang-stanfordUse when deciding where a MICRO paper's supporting material lives, because MICRO allows no appendix at all — triaging content into the 11 reviewed pages, the unlimited references, an anonymized artifact repository, or the post-acceptance two-page artifact appendix, and cutting what fits nowhere.
- ▌ Micro Writing Style · brycewang-stanfordUse when drafting or revising a MICRO paper's prose and structure — building the characterization-motivated introduction, budgeting 11 appendix-free pages, drawing the mechanism walkthrough a microarchitect can re-implement, and pairing every speedup claim with its area, storage, and power cost line.
- ▌ Micro Review Process · brycewang-stanfordUse when reasoning about how a MICRO submission is judged — the double-blind HotCRP pipeline from the April deadline through the June rebuttal/revision window to the early-July notification, what reviewers score in a microarchitecture paper, the professional-conduct rules, and how the new Industry Track review differs.
- ▌ Micro Author Response · brycewang-stanfordUse when reviews arrive for a MICRO submission and the rebuttal/revision window opens — triaging reviewer objections by what can change a decision, answering methodology attacks with runs and configs rather than promises, keeping anonymity intact, and staying inside MICRO's professional-conduct rules for rebuttals.
- ▌ Micro Reproducibility · brycewang-stanfordUse when hardening a MICRO paper's results for re-derivation — pinning simulator commits and configs, recording workload trace provenance and SimPoint recipes, versioning power/area models, capturing RTL toolchain state, and writing the run manifests that later survive MICRO's post-acceptance artifact evaluation.
- ▌ Micro Topic Selection · brycewang-stanfordUse when deciding whether a project belongs at MICRO (IEEE/ACM International Symposium on Microarchitecture) or should route to ISCA, HPCA, ASPLOS, DAC/ICCAD, SC, or MLSys — testing whether the mechanism truly lives inside the machine, gauging the MICRO evidence bar, and weighing the main track against the new Industry Track.
- ▌ Micro Artifact Evaluation · brycewang-stanfordUse when preparing a MICRO artifact for post-acceptance evaluation — packaging simulators, configs, traces, and scripts so evaluators can regenerate the paper's figures, targeting the ACM Available/Functional/Reproducible badges, handling licensed workloads and long simulations, and earning the optional artifact appendix.