infocom-workflow
Use when planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December notification, the IEEE Xplore camera-ready with PDF eXpress and eCF, and presentation, with backward-planning offsets for a networking paper and honest handling of the single-summer deadline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.
# INFOCOM Workflow Use this as the project-management skill for an INFOCOM submission. Replace every date with the current official timetable and work backwards from the **abstract/metadata deadline** (in late July), which precedes the full-paper deadline by about a week. INFOCOM runs a **single annual summer deadline**, so a missed cycle costs roughly a year — plan the calendar as tightly as the paper. INFOCOM is an IEEE ComSoc conference with **no standing editor-in-chief** and **no article-processing charge**. Rotating leadership is the per-edition General Co-Chairs and TPC Co-Chairs, appointed under ComSoc; the cost model is **conference registration**, and at least one author must register for the paper to enter IEEE Xplore. Chairs rotate yearly; re-check the organizing-committee page rather than carrying a name forward. ## Milestones - **Venue fit:** confirm INFOCOM over SIGCOMM/NSDI/MobiCom and confirm the paper is ready this cycle (`infocom-topic-selection`). - **Evidence lock:** freeze the system model, theorems/proofs, simulator setup, baselines, and the evaluation results. - **Abstract/metadata registration:** enter real title, abstract (≤200 words), co-authors, and topi
- Milestones
- Backward plan from the full-paper deadline
- The single-summer calendar reality
- Failure modes by stage
- Coordination notes
- Output format
What does the infocom-workflow skill do?
Use when planning an IEEE INFOCOM project timeline from venue fit through the two-step EDAS abstract-then-paper registration, the early-reject checkpoint, the December notification, the IEEE Xplore camera-ready with PDF eXpress and eCF, and presentation, with backward-planning offsets for a networking paper and honest handling of the single-summer deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.