ipsn-workflow
Use when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-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.
# IPSN Workflow Use this as the project-management skill for an IPSN-lineage submission. Replace every date with the current official timetable and work backwards from the successor (SenSys) deadline at **CPS-IoT Week**. The single biggest planning fact: **IPSN no longer runs standalone** — it merged into **SenSys (Embedded AI and Sensing Systems)**, so plan against the current SenSys call, keeping the IP-vs-SPOTS instinct. IPSN had **no standing editor-in-chief** and **no APC**; rotating leadership was the per-edition General Chair(s) and per-track (IP / SPOTS) Program Chairs under CPS-IoT Week, ACM SIGBED, and IEEE. The cost model is registration; at least one author presents. Re-check the successor's organizing-committee page rather than carrying a name forward. ## Milestones - **Venue + track fit:** confirm the IPSN lineage over MobiSys/MobiCom/INFOCOM/RTAS, and pick IP vs SPOTS (`ipsn-topic-selection`). - **Evidence lock:** freeze the testbed, ground-truth reference, baselines, energy/latency measurement setup, and the dataset/firmware artifact contents. - **Deployment window (if applicable):** schedule field time early — a bridge, building, or wildlife deployment cannot be re
- Milestones
- Backward plan from the submission deadline
- The merger and calendar reality
- Failure modes by stage
- Coordination notes
- Output format
What does the ipsn-workflow skill do?
Use when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-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.