isca-workflow
Use when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.
# ISCA Workflow An ISCA year has one gate. Miss mid-November and the next identical opportunity is twelve months away, which is why experienced groups treat the ISCA calendar as an engineering schedule with the deadline as tape-out. This skill lays out that schedule using the verified ISCA 2026 dates as the template; as of 2026-07-08 the ISCA 2027 CFP was not yet posted, so every 2027 date below is an expectation to confirm against `iscaconf.org/isca2027/` the moment it exists (待核实). ## The verified 2026-cycle skeleton | Milestone | ISCA 2026 date (verified) | What it means operationally | |---|---|---| | Abstract registration | November 10, 2025 | Title, abstract, authors, conflicts locked in HotCRP; paper content still fluid | | Full paper | November 17, 2025 | The reviewed PDF — one week after abstracts, so the abstract week is a writing week, not a buffer | | Round 1 reviews due | December 19, 2025 | First reviewer wave completes before the holidays | | Round 2 reviews due | February 13, 2026 | Additional reviews on papers that advanced | | Rebuttal + revision | February 16 - March 6, 2026 | Authors see reviews, respond, and may revise — a three-week working window | | Conferen
- The verified 2026-cycle skeleton
- Working backward from November
- The winter: silence, then three loud weeks
- Branch plans after notification
- Team ledger
- Failure modes this calendar prevents
- Milestone-to-skill routing
What does the isca-workflow skill do?
Use when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.