naacl-workflow
Use when planning a research project's calendar toward NAACL — handling the chapter's skipped-year rhythm, choosing an ARR cycle when the edition's feeding cycles are not yet announced, backward-planning data and annotation work, and keeping a decision tree for commit-versus-wait-versus-reroute moments.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-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.
# NAACL Workflow Project management for NAACL differs from every annual venue in one blunt way: the conference might not exist next year. The chapter historically skips editions when the ACL main meeting is hosted in the Americas — no NAACL 2023, no NAACL 2026 — so a NAACL plan is really a plan for entering the *ACL Rolling Review machine at a moment that leaves a NAACL commitment open, with named fallbacks for when the calendar shifts under you. ## The calendar reality (as of 2026-07-08) - Most recent editions: NAACL 2024 (Mexico City, June 16-21, 2024) and NAACL 2025 (Albuquerque, April 29 - May 4, 2025). - Next edition: NAACL 2027 — site registered, but dates, venue, feeding cycles, and commitment deadline all 待核实 at planning time. - Reference shape from 2025: ARR upload mid-October, reviews mid-December, commitment around the turn of the year, final versions early February, conference late April. A spring NAACL implies an autumn ARR deadline — plan provisionally on that shape, verify the moment the CFP lands. ```text Provisional backward plan for a spring NAACL (verify every date): T-0 conference (spring) T-11w final versions due T-16w commitment deadline <- reviews must exist
- The calendar reality (as of 2026-07-08)
- Milestones with owners
- The commit-versus-wait decision tree
- Monitoring routine between editions
- Standing risks on a NAACL path
- Output format
What does the naacl-workflow skill do?
Use when planning a research project's calendar toward NAACL — handling the chapter's skipped-year rhythm, choosing an ARR cycle when the edition's feeding cycles are not yet announced, backward-planning data and annotation work, and keeping a decision tree for commit-versus-wait-versus-reroute moments.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill naacl-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.