pldi-workflow
Use when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-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.
# PLDI Workflow PLDI is an annual, single-deadline venue with a long tail: the paper is due in November, but the project is not finished until the PACMPL article, the badged Zenodo artifact, and the June talk have all shipped. Plan all three from the start. Anchor dates below are the 2026 cycle (deadline Nov 13, 2025; response Feb 17-21, 2026; notification Mar 5, 2026; registration opened Mar 16; conference in Boulder Jun 15-19, 2026) — reread the current dates page before scheduling anything, and note that PLDI 2027's calendar was unpublished as of 2026-07-08 (待核实). PLDI has no standing editor-in-chief and charges no submission fee; leadership rotates per edition (2026: General Chair Bor-Yuh Evan Chang, Program Chair Manu Sridharan), the conference is funded through registration, and the PACMPL open-access cost is handled through SIGPLAN/ACM Open arrangements at camera-ready time (`pldi-camera-ready`), not at submission. ## Backward plan from the November deadline | Weeks out | Milestone for a compiler/analysis paper | |---|---| | 12+ | Mechanism frozen; running example chosen; suite + baselines locked (`pldi-experiments`) | | 8 | Implementation feature-complete on the suite; meas
- Backward plan from the November deadline
- The long tail after the deadline
- Ownership map
- Rejection routing
- Output format
What does the pldi-workflow skill do?
Use when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-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.