colm-workflow
Use when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July decisions, August camera-ready, and October conference, coordinating co-authors, compute, and reciprocal-reviewing duties, and slotting COLM into a multi-venue LM-research pipeline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-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.
# COLM Workflow COLM gives you exactly one shot per year: one deadline (late March in 2026), one rebuttal, one decision (early July), one October stage. Campaign planning is therefore mostly *backward induction from March* — and, because LM projects burn compute and involve many hands, the critical path is usually GPUs and co-author availability, not writing. ## The 2026 cycle as a template (all dates verified 2026-07-08) | Date (2026) | Event | What must already be true | |---|---|---| | February | OpenReview opens | Profiles current for every author | | March 26 | Abstract deadline | Real abstract; reciprocal reviewer chosen | | March 31 | Full paper deadline | Frozen claims, pinned evidence, anonymized package | | May 22 | Reviews released | Response owners pre-assigned; cache warm | | May 22 - June 8 | Rebuttal | ~18 days; plan in `colm-author-response` | | July 8 | Decisions | Both branches pre-planned | | August 7 | Camera-ready | Public artifacts ready to ship simultaneously | | October 6-9 | Conference, San Francisco | Presenter, visa, poster all handled | **Live-phase note:** on this pack's access date — 2026-07-08 — the 2026 cycle is at decision day. If that is you, jump
- The 2026 cycle as a template (all dates verified 2026-07-08)
- Backward plan from a March deadline
- Coordination artifacts for a multi-author LM paper
- Slotting COLM into the venue year
- The small-lab variant
- Failure patterns this calendar produces
- Workshop track as a parallel lane
- Output format
What does the colm-workflow skill do?
Use when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July decisions, August camera-ready, and October conference, coordinating co-authors, compute, and reciprocal-reviewing duties, and slotting COLM into a multi-venue LM-research pipeline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-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.