icse-workflow
Use when planning an ICSE research-track campaign end to end, covering the single-cycle calendar from the June abstract deadline through September response, October decisions, the November revision sprint, artifact evaluation, camera-ready, and the April conference, plus rerouting timelines after rejection.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-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.
# ICSE Workflow An ICSE campaign is a ten-month pipeline with one entrance. The 2027 cycle (checked 2026-07-08 against the official dates pages) runs a **single submission cycle** — a change from the two-cycle 2025/2026 model — so a missed June deadline costs a full year, and the calendar below is the whole game. ## The 2027-cycle master calendar | Date (all AoE where applicable) | Milestone | Your workstream | |---|---|---| | Jun 23, 2026 | Abstract (mandatory) | Real title + abstract frozen | | Jun 30, 2026 | Full paper deadline | 10+2 IEEE PDF, artifact link live | | Jul–Aug 2026 | Reviews written | Prepare response infrastructure; rest | | Sep 2026 | Author response window | Criterion-mapped replies (`icse-author-response`) | | Oct 20, 2026 | Decisions: Accept / Major Revision / Reject | Branch: celebrate / sprint / reroute | | Nov 17, 2026 | Major Revision due | Four-week revision sprint | | Dec 18, 2026 | Final MR decisions | Terminal for the cycle | | Early 2027 (待核实) | Artifact evaluation window | Badge submission (`icse-artifact-evaluation`) | | 待核实 | Camera-ready due | +1 page allowance, IEEE production | | Apr 25 – May 1, 2027 | ICSE in Dublin (core Apr 28–30) | Talk, ar
- The 2027-cycle master calendar
- Working backward from June 30
- Role assignments that prevent deadline-week chaos
- Branch plans after October 20
- Cadence between milestones
- Cycle-volatility warnings
- Output format
What does the icse-workflow skill do?
Use when planning an ICSE research-track campaign end to end, covering the single-cycle calendar from the June abstract deadline through September response, October decisions, the November revision sprint, artifact evaluation, camera-ready, and the April conference, plus rerouting timelines after rejection.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-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.