icassp-workflow
Use when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring notification, IEEE Xplore camera-ready, and the May conference — with backward-planning offsets and the choice among standard, OJSP-ICASSP, and grand-challenge tracks.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-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.
# ICASSP Workflow Use this as the project-management skill for an ICASSP submission. Replace every date with the current official timetable and work backward from the paper deadline. ICASSP is an **IEEE Signal Processing Society conference**, rebuilt by a new local committee each year; it has no standing editor-in-chief, and the cost model is registration, with the proceedings paper published in IEEE Xplore. ## The annual clock (2026-cycle shape, verify each year) - **September** — full-paper deadline on the CMS portal (ICASSP 2026: 17 Sep 2025; **ICASSP 2027 reported ~16 Sep 2026, the next major gate as of 2026-07-09**). - **Autumn/early winter** — single-blind technical-committee review. - **December** — short rebuttal/author-response window (2026 cycle: reported to ~22 Dec 2025), if the cycle runs one. - **Late winter** — notification; accepted-paper revision window (2026: to ~28 Jan 2026). - **Spring** — IEEE Xplore camera-ready (PDF eXpress + IEEE copyright form), registration. - **May** — the conference; in-person oral or poster presentation (ICASSP 2026 Barcelona, 4-8 May; ICASSP 2027 Toronto, 16-21 May). ## Milestones - **Venue fit** — confirm the contribution is genuinely
- The annual clock (2026-cycle shape, verify each year)
- Milestones
- Backward plan from the September deadline
- Track decision (decide before the deadline)
- Failure modes by stage
- Coordination notes
- Output format
- Currency note
What does the icassp-workflow skill do?
Use when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring notification, IEEE Xplore camera-ready, and the May conference — with backward-planning offsets and the choice among standard, OJSP-ICASSP, and grand-challenge tracks.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-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.