pods-workflow
Use when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour rebuttal, the accept/reject/revision decision and shepherded revision round, PACMMOD-track publication, the arXiv full version, and presentation — with backward-planning offsets for a theory paper and honest handling of cycle choice.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-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.
# PODS Workflow Use this as the project-management skill for a PODS submission. Replace every date with the current official timetable and work backwards from the **abstract** deadline, which precedes the full-paper deadline by about a week in each cycle. PODS runs **multiple submission cycles per year** and every paper may hit a **revision** round with a shepherd, so plan for a two-round-per-cycle process, not a single accept/reject. PODS is a symposium whose papers are journal articles in the **PACMMOD PODS track**: it has **no standing editor-in-chief** and no APC in the systems sense. Rotating leadership is the per-edition PODS PC Chair (PODS 2026: Ke Yi, HKUST, verified 2026-07-09) appointed with ACM SIGMOD and SIGACT; the cost model is registration and at least one author presents. Chairs rotate yearly — re-check the organization page rather than carrying a name forward. ## Choosing a cycle PODS's multi-cycle calendar is a planning lever, not just a constraint. As of 2026-07-09, PODS 2026 (Bengaluru) has already met, so the live target is **PODS 2027** (Huntington Beach): Cycle 1 closed 30 May 2026, and **Cycle 2 (abstract+COI 10 Oct 2026, paper 17 Oct 2026) is the next live
- Choosing a cycle
- Milestones
- Backward plan from the paper deadline
- Failure modes by stage
- Coordination notes
- Output format
What does the pods-workflow skill do?
Use when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour rebuttal, the accept/reject/revision decision and shepherded revision round, PACMMOD-track publication, the arXiv full version, and presentation — with backward-planning offsets for a theory paper and honest handling of cycle choice.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-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.