icdm-workflow
Use when planning an ICDM (IEEE International Conference on Data Mining) project timeline from venue fit through the abstract and full-paper deadlines, the long summer wait to the August notification, the no-rebuttal review, the possible short-paper acceptance branch, IEEE camera-ready, and in-person presentation on a single annual deadline.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-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.
# ICDM Workflow Use this as the project-management skill for an ICDM submission. ICDM runs a **single annual deadline**, so the plan is a one-shot sprint to June and then a long wait, not a KDD-style cycle loop. Replace every date with the current edition's official timetable and work backwards from the paper deadline. ICDM is an IEEE conference, not a journal: there is no standing editor-in-chief and no article-processing charge. The rotating analogue is the per-edition **General Chairs and Program (PC) Co-Chairs**, appointed anew each year (2026 chairs 待核实 on the committee page); the cost model is **registration**, and at least one author must present in person for the paper to appear in the IEEE proceedings. ## Milestones (2026 anchors — verify live) - Venue + track fit: confirm Research vs Applied vs Blue Sky (see `icdm-topic-selection`). - Evidence lock: freeze the mining task, mechanism, baselines, ablations, and scaling runs. - Abstract deadline (2026-05-30): register real title, abstract, authors, topics. - Full-paper deadline (2026-06-06, AoE): upload the anonymized 10-page PDF (Research). - The summer wait: reviews proceed triple-blind with, traditionally, **no rebuttal**
- Milestones (2026 anchors — verify live)
- Backward plan from the June paper deadline
- The two ICDM-specific branches
- Failure modes by stage
- Coordination notes
- Output format
What does the icdm-workflow skill do?
Use when planning an ICDM (IEEE International Conference on Data Mining) project timeline from venue fit through the abstract and full-paper deadlines, the long summer wait to the August notification, the no-rebuttal review, the possible short-paper acceptance branch, IEEE camera-ready, and in-person presentation on a single annual deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icdm-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.