icde-workflow
Use when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible revise-and-resubmit window, and backward-planning a data-engineering systems paper from CMT submission through review, camera-ready, and IEEE Xplore publication.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-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.
# ICDE Workflow Use this as the project-management skill for an ICDE research submission. Replace every date with the current edition's official timetable and plan backward from the round you target. ICDE is a conference, not a journal-of-the-conference: it has no standing editor-in-chief and no article-processing charge. Leadership rotates per edition (General and Program Chairs named on each `icdeYYYY.github.io` site), the cost model is registration, and accepted papers publish in **IEEE Xplore** — not in a PACMMOD- or PVLDB-style venue journal. Re-check the current organization page rather than carrying a name forward. ## The two-round unit Unlike SIGMOD's four quarterly PACMMOD rounds or PVLDB's twelve monthly deadlines, ICDE gives you **two shots per edition** and no more. ICDE 2027's Round 1 paper deadline was June 11, 2026; Round 2 is November 11, 2026 with notification February 10, 2027. Because a Round 1 reject cannot re-enter Round 2, the round choice is a real commitment, not a convenience. ## Milestones - **Venue and round fit:** confirm the contribution is a data-management primitive and that the chosen round is reachable without rushing the evaluation. - **Evidence lo
- The two-round unit
- Milestones
- Backward plan from the round paper deadline
- Revision-bandwidth reasoning
- Failure modes by stage
- Output format
What does the icde-workflow skill do?
Use when planning an IEEE ICDE project timeline around the two-round-per-edition calendar, choosing between the June and November research deadlines, budgeting for a possible revise-and-resubmit window, and backward-planning a data-engineering systems paper from CMT submission through review, camera-ready, and IEEE Xplore publication.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-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.