ijoc-workflow
Use when deciding which ijoc-* sub-skill to invoke next, or when sequencing a manuscript from idea through rebuttal for an INFORMS Journal on Computing (IJOC) submission. Routes — it does not replace — the specialized skills.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when deciding which ijoc-* sub-skill to invoke next, or when sequencing a manuscript from idea through rebuttal for an INFORMS Journal on Computing (IJOC) submission. Routes — it does not replace — the specialized skills.
Use when preparing an ACM IMC artifact for release, covering the artifact-availability declaration, post-acceptance availability shepherding, DOI-issuing dataset archives, documenting measurement provenance and vantage points, Community Contribution Award eligibility, and the difference between the anonymized review artifact and the public release.
Use when deciding which imfer-* sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for an IMF Economic Review (IMFER) submission. Routes — it does not replace — the specialized skills.
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.
Use when an INTERSPEECH paper is accepted and the camera-ready, registration, and presentation chain begins — de-anonymizing for the ISCA Archive, restoring acknowledgments on the references page, meeting the author-registration requirement for proceedings inclusion, DOI metadata, and oral/poster preparation for the conference week.
Use when managing an INTERSPEECH project across the annual ISCA cycle — backward-planning from the late-February deadline through the update window, spring review, June notification, camera-ready and registration coupling, and the September–October conference, including what to do in the current post-decision phase and 2027 planning.
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.
Use when ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix, deciding between textual rebuttal and a revised PDF with new experiments, structuring responses that arm a champion at the PC meeting, and avoiding window-burning mistakes.
Use when deciding what accompanies an ISCA submission beyond the 11 reviewed pages — what must live inside the page budget because reviewers see nothing else, how to use fully anonymized artifact links under the double-blind rules, staging material for the revision window, and planning post-acceptance release.
Use when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.