popl-workflow
Use when planning a POPL campaign calendar — backward-scheduling theory and mechanization from the July deadline, riding the October notification into the conditional-acceptance revision and artifact evaluation, landing the January conference, and retargeting across the SIGPLAN/PACMPL deadline wheel if July slips.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-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.
# POPL Workflow POPL's seat in the SIGPLAN year is fixed and unforgiving: **submit in July, hear in early October, revise and package artifacts in the fall, present in January**. For POPL 2027 (verified 2026-07-08): deadline July 9, 2026 AoE; notification October 5, 2026; symposium January 10-16, 2027, Mexico City. There is no abstract deadline and no second call. POPL is a conference — no editor-in-chief, no submission fee; the chairs rotate per edition (2027 names 待核实) and publication costs run through PACMPL's open-access model, not author-facing page charges in the normal case. ## Backward plan from a July deadline | Weeks before deadline | Theory-paper milestone | |---|---| | 16+ | Core calculus stable; main theorem conjectured precisely | | 12 | Hard lemmas proved on paper; mechanization of the kernel started | | 8 | Main theorem proved; decide mechanize-vs-hand-prove split per theorem | | 6 | Case studies or prototype evidence frozen (`popl-experiments`) | | 4 | Full draft in acmsmall; informal-to-formal ramp reviewed by an outsider | | 2 | Mock review by someone who tries to break the theorem, not the prose | | 1 | Anonymity sweep of paper + proof archive; correspondence ta
- Backward plan from a July deadline
- The fall gauntlet (acceptance path)
- If July slips: the PACMPL deadline wheel
- Output format
What does the popl-workflow skill do?
Use when planning a POPL campaign calendar — backward-scheduling theory and mechanization from the July deadline, riding the October notification into the conditional-acceptance revision and artifact evaluation, landing the January conference, and retargeting across the SIGPLAN/PACMPL deadline wheel if July slips.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-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.