fast-workflow
Use when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a one-shot revision, artifact evaluation, and the open-access camera-ready, with backward-planning offsets tuned to storage evaluation and honest handling of the two-deadline cycle.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-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.
# FAST Workflow Use this as the project-management skill for a FAST submission. Replace every date with the current official timetable and work backwards from the deadline you choose. FAST — the USENIX Conference on File and Storage Technologies — runs **two deadlines a year**, has an **author-response** period, and can issue a **one-shot revision** that spans into the next deadline, so plan for a longer arc than a plain accept/reject conference. FAST is a USENIX conference: it has **no standing editor-in-chief** and **no article-processing charge**. Rotating leadership is the per-edition Program Co-Chairs and the program committee, and the cost model is registration plus USENIX membership — proceedings are open access. Chairs and the Artifact Evaluation Committee rotate yearly; re-check the current committee page rather than carrying a name forward (FAST '27 rosters: **待核实** beyond what the CFP names). ## Choose the deadline, then plan backward FAST '27 offers **Spring** (submit 17 Mar 2026, notify 4 Jun 2026, final files 28 Jul 2026) and **Fall** (submit 15 Sep 2026, notify 8 Dec 2026, final files 26 Jan 2027). Pick by *evidence readiness* — storage measurements at steady state o
- Choose the deadline, then plan backward
- Milestones
- Backward plan from the submission deadline
- The two-deadline reality and one-shot revision
- Failure modes by stage
- Coordination notes
- Output format
What does the fast-workflow skill do?
Use when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a one-shot revision, artifact evaluation, and the open-access camera-ready, with backward-planning offsets tuned to storage evaluation and honest handling of the two-deadline cycle.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-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.