icsme-workflow
Use when planning an IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal, notification, IEEE Xplore camera-ready, the ROSE-Festival artifact evaluation, and presentation, with backward-planning offsets for a maintenance/evolution paper and honest handling of the single-annual-round calendar.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-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.
# ICSME Workflow Use this as the project-management skill for an ICSME submission. Replace every date with the current official timetable and work backwards from the EasyChair **abstract** cutoff — which precedes the paper deadline. ICSME runs a **single annual research round** with **no journal-style Major Revision**: a paper is accepted or rejected in one cycle, so front-load the evidence and plan the author-response rebuttal, not a revise-and-resubmit. ICSME is an IEEE conference with **no standing editor-in-chief** and no APC: proceedings go to IEEE Xplore and the cost model is registration. Rotating leadership is the per-edition General and Program Co-Chairs (ICSME 2026 committee roster **待核实** on the access date); re-check the organizing-committee page rather than carrying names forward. ICSME 2026 is the **42nd** edition in **Benevento, Italy** (University of Sannio), **14-18 September 2026**, co-located with SCAM and VISSOFT. ## Milestones - **Venue and track fit:** confirm ICSME over ICSE/FSE/SANER/MSR and pick the track — research, Journal-First, Registered Reports, RENE, NIER, tool-demo, or industry (`icsme-topic-selection`). - **Evidence lock:** freeze research question
- Milestones
- Backward plan from the paper deadline
- The single-round calendar reality
- Failure modes by stage
- Coordination notes
- Output format
What does the icsme-workflow skill do?
Use when planning an IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal, notification, IEEE Xplore camera-ready, the ROSE-Festival artifact evaluation, and presentation, with backward-planning offsets for a maintenance/evolution paper and honest handling of the single-annual-round calendar.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-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.