isca-related-work
Use when positioning an ISCA submission against prior art — covering five decades of architecture literature across ACM DL, IEEE Xplore, and dblp, differentiating by mechanism rather than metric, handling self-citations and arXiv preprints under double-blind rules, and exploiting ISCA's unlimited reference pages.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-related-work --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.
# ISCA Related Work Architecture is an old field with a long memory. ISCA has run since 1973, its committee members have often worked an area for twenty years, and the fastest way to lose a reviewer is to present a mechanism they saw under another name in a proceedings they attended. Positioning at this venue is therefore archaeology first, differentiation second. ## Search across three catalogs, because ISCA lives in two publishers ISCA's dual ACM/IEEE sponsorship means its proceedings are split across publisher libraries by edition (the 52nd, Tokyo 2025, was ACM-published; the 2026 edition carried IEEE branding — the pattern alternates). Consequences for search: - **dblp** (`dblp.org/db/conf/isca/`) is the reliable spine: complete, per-edition, publisher-neutral. Start every sweep there. - **ACM DL and IEEE Xplore** each hold only part of the canon; searching one and concluding "no prior work" is a classic self-inflicted wound. - Sweep the sibling venues as first-class citizens — MICRO, HPCA, ASPLOS — plus the journals where architecture ideas resurface (TACO, CAL, TC, IEEE Micro including its annual Top Picks selections). - Finish with a recent-window arXiv pass: concurrent prep
- Search across three catalogs, because ISCA lives in two publishers
- The lineage paragraph reviewers actually want
- Where comparison belongs
- Double-blind mechanics, ISCA 2026 wording
- Building the map before writing the section
- Using the unlimited reference pages
- Timing and the November reality
- Section self-check
- Positioning output
Blind-voice audit over the LaTeX source
grep -nEi 'our (prior|previous|earlier|recent) (work|paper|design|study)' *.tex
grep -nEi 'we (previously|earlier) (showed|proposed|presented)' *.tex
grep -nE 'github\.com|gitlab\.com|bitbucket|\.edu/~[a-z]' *.tex *.bib
Coverage sanity: in-text citation keys that never resolve
grep -oE '\\cite[tp]?\{[^}]*\}' *.tex | tr ',' '\n' | sort -u | wc -lWhat does the isca-related-work skill do?
Use when positioning an ISCA submission against prior art — covering five decades of architecture literature across ACM DL, IEEE Xplore, and dblp, differentiating by mechanism rather than metric, handling self-citations and arXiv preprints under double-blind rules, and exploiting ISCA's unlimited reference pages.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-related-work --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.