hpca-related-work
Use when building an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore, writing lineage paragraphs with structural deltas, blinding self-citations without touching the bibliography, and honoring the rule that every reference lists all its authors.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-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.
# HPCA Related Work Use this to position an HPCA paper against decades of computer-architecture literature. The bar is a related-work section that reads as a **lineage with structural deltas**, not a citation pile — and one that respects HPCA's two bibliography rules: references are never blinded, and every reference lists all of its authors. ## Sweep the whole architecture record Architecture ideas recur across four venues and forty years. Search the **publisher-neutral spine (dblp)** plus **IEEE Xplore**, not a single library: - dblp HPCA series (`dblp.org/db/conf/hpca/`) for the venue's own line, and the ISCA/MICRO/ASPLOS series for cross-venue lineage. - IEEE Xplore for HPCA's published volumes; ACM DL for the ACM-published siblings. - The HPCA Test of Time Award list for the load-bearing ancestors of your subfield. A mechanism you think is new often has a named ancestor at HPCA 2003 or ISCA 2006; find it before a reviewer does. ## Write lineage, not a pile Each related-work paragraph should name a prior line, then state the **structural delta** your paper adds — what changes in the machine or the mechanism, not just that you are "different." Group by mechanism family, not chro
- Sweep the whole architecture record
- Write lineage, not a pile
- Blind the voice, never the bibliography
- The concurrency and preprint question
- Build sequence
- Output format
What does the hpca-related-work skill do?
Use when building an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore, writing lineage paragraphs with structural deltas, blinding self-citations without touching the bibliography, and honoring the rule that every reference lists all its authors.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-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.