usenixsec-workflow
Installation
SKILL.md
USENIX Security Workflow
USENIX Security runs two independent submission cycles per year, so "when do we submit?" is a real strategic choice, not a fixed date. This skill turns a target cycle into a dated backward plan and assigns owners to the venue-specific risks. Dates below are the '26/'27 cycle values read on 2026-07-08 (via search renderings; usenix.org direct fetch 403'd) — reconfirm against the live CFP.
Step 1: pick the cycle
| Consideration | Favors the earlier cycle | Favors the later cycle |
|---|---|---|
| Readiness | Evaluation truly done now | Needs one more experiment done right |
| Conference lead time | Cycle-1 accepts publish ~7 months pre-symposium | Cycle-2 accepts closer to the event |
| Competing deadlines | Avoids clashing with a CCS/S&P/NDSS date | Room to route a reject to the next venue |
| Resubmission runway | Reject still leaves the same-year second cycle open* | Reject pushes to next year |