percom-workflow
Use when planning an IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE Xplore camera-ready, and in-person presentation, with backward-planning offsets for a human-subjects sensing paper and honest handling of the single-annual-deadline cycle.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-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.
# PerCom Workflow Use this as the project-management skill for a PerCom submission. Replace every date with the current official timetable and work backwards from the HotCRP **registration** cutoff — which precedes the paper deadline by about a week. PerCom runs a **single annual deadline** feeding one review round with a **bounded rebuttal** and an **early-rejection gate**; there is no journal-style revision, so plan for the paper to be complete at submission. PerCom is an IEEE Computer Society conference: it has **no standing editor-in-chief** and **no APC** in the open-access sense. Rotating leadership is the per-edition General and TPC (Program) Co-Chairs (PerCom 2027 full roster **待核实** as of 2026-07-09), and the cost model is IEEE registration with at least one author presenting **in person**. ## Milestones - **Venue fit:** confirm PerCom over ACM UbiComp/IMWUT, MobiCom, SenSys, or IPSN, and confirm the paper is ready this cycle (`percom-topic-selection`). - **Data collection lock:** IRB/consent secured, subjects recruited, sensing protocol frozen — the long pole for a human-subjects paper. - **Evidence lock:** freeze claims, cross-subject splits, baselines, metrics, limitati
- Milestones
- Backward plan from the submission deadline
- Cycle reality: one shot per year, gated early
- Failure modes by stage
- Coordination notes
- Output format
What does the percom-workflow skill do?
Use when planning an IEEE PerCom project timeline from venue fit through paper registration, the September submission, the early-rejection gate, the bounded rebuttal, the IEEE Xplore camera-ready, and in-person presentation, with backward-planning offsets for a human-subjects sensing 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 percom-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.