humrel-workflow
Use when deciding which humrel-* sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Human Relations (HR) 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 humrel-* sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Human Relations (HR) submission. Routes — it does not replace — the specialized skills.
Use when planning an ICALP (EATCS) campaign backward from its single annual February deadline, through abstract registration, the anonymous submission, the Track B rebuttal window, the April notification, and the LIPIcs camera-ready and presentation, and when coordinating a full-version (arXiv/ECCC) release alongside the anonymous submission.
Use when planning an ICASSP project timeline — the annual clock from venue fit through the September paper deadline, single-blind review, the short winter rebuttal, spring notification, IEEE Xplore camera-ready, and the May conference — with backward-planning offsets and the choice among standard, OJSP-ICASSP, and grand-challenge tracks.
Use when an ICCV paper is accepted and the final version, releases, and October conference must be delivered, covering de-anonymization edits, the summer camera-ready window between June decisions and the autumn meeting, CVF open access plus IEEE Xplore publication, arXiv synchronization after the embargo lifts, and presenting at an international venue.
Use when designing the experimental program for an ICCV paper against the early-March deadline, covering benchmark-drift audits across the two-year gap, baseline fairness in the foundation-model era, ablations that isolate mechanisms, qualitative and failure evidence, and sequencing runs so the decisive result lands before the deadline, not after.
Use when planning or auditing ICCV supplementary material under the same-day paper-plus-supplement deadline, covering what moves out of the 8-page body, parallel production of videos and code from February onward, double-blind hygiene inside the archive, and making depth material navigable for reviewers who choose to open it.
Use when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.
Use when planning an ICDM (IEEE International Conference on Data Mining) project timeline from venue fit through the abstract and full-paper deadlines, the long summer wait to the August notification, the no-rebuttal review, the possible short-paper acceptance branch, IEEE camera-ready, and in-person presentation on a single annual deadline.
Use when auditing an ICDT (International Conference on Database Theory) regular-paper submission for Microsoft CMT readiness, covering the two-step abstract-then-paper deadline in the correct submission cycle, the lipics-v2021 15-page limit excluding references, the clearly-marked appendix read at the PC's discretion, anonymous submission since 2024, the complete-proofs / full-version expectation, and which submission problems are unfixable after the AoE cutoff.
Use when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact release. Use when sequencing milestones against the current cycle's OpenReview deadlines, budgeting time for the long public discussion phase, or assigning owners for anonymity audits and reviewer-verifiable evidence paths.