cscw-workflow
Use when planning a CSCW submission timeline end to end — the PACMHCI journal model, the retired fixed cycles versus the rolling 2027+ pathway, Revise-and-Resubmit rounds that span months, and back-planning so an acceptance lands before the conference-year presentation cutoff.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-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.
# CSCW Workflow CSCW is not a deadline sprint. Since 2017 its papers have been journal articles in PACMHCI, and since early 2026 the venue has been rolling out a fully journal-style pipeline: **submit whenever the paper is ready, expect a decision in roughly 3-4 months, revise on the editor's clock, and present at whichever conference your acceptance lands in front of.** Planning a CSCW project therefore means planning a *revision campaign*, not a submission night. ## The two regimes (as of 2026-07-08) | Aspect | Fixed cycles (through the May 2025 cycle) | Rolling (CSCW 2027 and beyond) | | --- | --- | --- | | Deadline | Hard cutoff (last: May 14, 2025, 12:00 EDT) | None — submit when ready | | Platform | PCS | Manuscript Central (mc.manuscriptcentral.com/pacmhci) | | Who handles the paper | Program committee (ACs) per cycle | Editorial board: EiC/AE by methodological track | | First decision | Batched (first-round decisions ~6 months in) | Rolling, ~3-4 months from submission | | Revision windows | Fixed dates (e.g., R&R due January 13, 2026) | Set per paper by the handling editor | | Conference tie | Cycle mapped to a specific conference year | Accepted papers invited to the *nex
- The two regimes (as of 2026-07-08)
- Cycle-hopping, translated for the rolling era
- Campaign plan skeleton
- Risks specific to this venue's shape
- Status-report format
What does the cscw-workflow skill do?
Use when planning a CSCW submission timeline end to end — the PACMHCI journal model, the retired fixed cycles versus the rolling 2027+ pathway, Revise-and-Resubmit rounds that span months, and back-planning so an acceptance lands before the conference-year presentation cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-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.