micro-workflow
Use 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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-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.
# MICRO Workflow MICRO owns the **autumn slot** of computer architecture's four-venue year: an early April deadline feeding an end-of-October symposium. Because the four sibling venues interleave, a MICRO plan is really a lattice plan — every outcome has a next move within roughly four months. Dates below verified 2026-07-08; every one is a single-cycle snapshot. ## The 2026 cycle clock (59th edition, Athens) ```text 2026-03-31 abstract registration 11:59 PM EDT hard gate 2026-04-07 full paper 11:59 PM EDT micro2026.hotcrp.com 2026-06-03 → 06-17 rebuttal/revision two-week window (micro-author-response) 2026-07-07 notification 2026-09-11 camera-ready (AE runs in parallel; micro-camera-ready) 2026-10-31 → 11-04 symposium, Athens, Greece ``` As of this pack's check date (2026-07-08), the 2026 cycle had **just issued decisions** — the live work is camera-ready + AE for accepts, and lattice routing for rejects. The next MICRO submission opportunity is the 2027 cycle, expected in the same early-April position (待核实 when `microarch.org` posts it). ## The four-venue calendar from MICRO's seat | Venue | Deadline (verified for cycle shown) | Conference | Use it when | |---|---|---|---| | **MI
- The 2026 cycle clock (59th edition, Athens)
- The four-venue calendar from MICRO's seat
- Backward plan for a MICRO 2027 submission
- Risk register for the compute-bound schedule
- Standing weekly cadence during a campaign
- Outcome branches (July 7 has happened)
- Multi-paper pipelines and self-competition
- Output format
What does the micro-workflow skill do?
Use 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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-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.