hpca-workflow
Use when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-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.
# HPCA Workflow Use this as the project-management skill for an HPCA submission. Replace every date with the current official timetable and plan backward from the late-July gate. HPCA is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. It is run by the IEEE-CS Technical Committee on Computer Architecture (TCCA); the rotating leadership is the per-ed
What does the hpca-workflow skill do?
Use when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-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.