edbt-workflow
Use when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-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.
# EDBT Workflow Use this as the project-management skill for an EDBT submission. EDBT's defining rhythm is the **multiple-cycle rolling model** (three cycles a year since 2022), so the first planning act is not "hit the deadline" but **"choose the cycle my evidence is ready for."** Replace every date with the current host-site timetable; the per-cycle author-feedback and revision windows are decided per edition. EDBT is a conference whose proceedings are **open access on OpenProceedings.org** (CC-BY-NC-ND, no APC): it has **no standing editor-in-chief**, the rotating leadership is the per-edition General and Program Chairs appointed with the EDBT Association, and the host site moves each year (Barcelona 2025, Tampere 2026). Re-check the current host page rather than carrying a name or URL forward. ## The cycle structure (one cycle, end to end) Each EDBT cycle runs the same five-step arc (EDBT 2022 timeline; reverify dates per edition): ```text [1] Submission upload PDF + artifact to Microsoft CMT by the cycle deadline [2] Author feedback phase a short window to respond to initial reviews [3] Notification #1 accept / REVISE / reject [4] Revised submission if REVISE: upload the revis
- The cycle structure (one cycle, end to end)
- Choosing a cycle
- Milestones
- Backward plan from a cycle deadline
- Cycle-hopping: the honest calendar reality
- Failure modes by stage
- Coordination notes
- Output format
What does the edbt-workflow skill do?
Use when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill edbt-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.