iccv-workflow
Use when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-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.
# ICCV Workflow An ICCV campaign runs on a spring-deadline, autumn-conference rhythm that only exists in odd years. The 2025 cycle — the most recent completed one, verified 2026-07-08 — ran: paper registration March 3, full submission **and** supplementary March 7 (11:59pm HST), reviews to authors May 9, rebuttal May 10–16, decisions late June, conference October 19–23 in Honolulu (workshops the 19th–20th, main program the 21st–23rd). ICCV 2027 is announced for Hong Kong in early October 2027; its deadline chain was unpublished at check time, so every date below is a 2025-cycle anchor for shape, not a promise. ## The autumn fork (the decision nobody schedules) The ICCV cycle actually begins the *previous autumn*, when the team must choose between the imminent CVPR deadline (November) and holding four more months for ICCV (March). Make the fork an explicit meeting with a written outcome: - Hold for ICCV when the missing evidence is real (a benchmark, a user study, a second domain) and four months genuinely closes it. - Take CVPR when the paper is submittable now — holding a finished paper four months in a field with weekly arXiv turnover is negative-expected-value. - Never split the
- The autumn fork (the decision nobody schedules)
- Cycle plan with owners (2025-shaped)
- Two ICCV-specific project risks
- International logistics are part of the plan
- The fallback ladder (the biennial part)
- Multi-paper labs, odd-year edition
- Reverify before trusting any date here
- Output format
What does the iccv-workflow skill do?
Use when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-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.