cav-workflow
Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-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.
# CAV Workflow Use this as the project-management skill for a CAV submission. Replace every date with the current official timetable and work backward from the AoE paper deadline. CAV publishes open access in **Springer LNCS**, reviews in **two stages** (an early-reject filter, then a rebuttal), and runs an **optional** artifact evaluation after notification — plan for all three, not just accept/reject. CAV is a conference with **no standing editor-in-chief**; the rotating leadership is the per-edition Program Chairs and Steering Committee. For CAV 2026 the Program Chairs are **Anthony W. Lin, Eva Darulova, and Philipp Rümmer** (verified 2026-07-09), and the venue is **Lisbon, part of FLoC 2026**. Chairs rotate yearly; re-check the organization page rather than carrying a name forward. ## Milestones - **Venue + category fit:** confirm CAV over TACAS/FMCAD/VMCAI and pick the category (Regular / Tool / Application / Industrial) (`cav-topic-selection`). - **Evidence lock:** freeze the theorem/algorithm, the benchmark set (revision pinned), the baseline tools and versions, the resource limits, and the artifact contents. - **Submission:** upload the LNCS-formatted PDF in the right categ
- Milestones
- Backward plan from the submission deadline
- The two-stage cycle: plan for the early reject
- Failure modes by stage
- Coordination notes
- Output format
What does the cav-workflow skill do?
Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-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.