← all publishers

brycewang-stanford

@brycewang-stanford source repo

Report this profile Claim this profile

• 5.3k skills
• 0 followers
• 1k repo stars
• 2 weeks ago last updated

1. ▌
   Wacv Experiments · brycewang-stanford

   Use when designing or auditing WACV experiments, covering Applications-track systems evidence (latency, power, robustness under real constraints) versus Algorithms-track matched-baseline novelty, comparative assessment under the deployed condition, uncertainty over seeds and sessions, ablations, and evidence that survives the two-round review.
   1k repo stars
2. ▌
   Wsdm Experiments · brycewang-stanford

   Use when designing or auditing the evaluation of a WSDM paper - offline ranking and recommendation metrics with bias controls, temporal-split protocols for interaction logs, baseline selection from recent WSDM/SIGIR/KDD editions, ablations that isolate the mechanism, efficiency reporting, and online-evidence framing.
   1k repo stars
3. ▌
   Aaai Camera Ready · brycewang-stanford

   Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.
   1k repo stars
4. ▌
   Aaai Related Work · brycewang-stanford

   Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.
   1k repo stars
5. ▌
   Aamas Submission · brycewang-stanford

   Use when auditing an AAMAS main-track submission for OpenReview readiness, the 8-page-plus-references limit, the full-paper versus 2-page extended-abstract choice, double-blind anonymity, the supplementary zip cap, track fit across the AAAI/JAAMAS/Blue Sky tracks, dual-submission rules, and desk-reject triggers before upload.
   1k repo stars
6. ▌
   Acl Review Process · brycewang-stanford

   Use when reasoning about how an ACL paper travels through ACL Rolling Review and conference commitment, covering reviewer and area-chair roles, meta-reviews, the commitment decision by senior area chairs and program chairs, Findings versus main-conference outcomes, ethics review escalation, and resubmission strategy across cycles.
   1k repo stars
7. ▌
   Ccs Submission · brycewang-stanford

   Use when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics considerations appendix, artifact-availability posture, dual-submission policy, per-cycle submission caps, desk-reject triggers, and final-week sequencing.
   1k repo stars
8. ▌
   Ase Review Process · brycewang-stanford

   Use when reasoning about how an ASE (IEEE/ACM Automated Software Engineering) research submission is evaluated, covering double-anonymous review, the early-rejection stage before rebuttal, the Accept / Revision / Reject outcomes, the criteria-bound revision round, and how ASE's process differs from FSE's PACMSE Major Revision, ICSE's cycles, and ISSTA's rounds.
   1k repo stars
9. ▌
   Asplos Workflow · brycewang-stanford

   Use when planning an ASPLOS campaign across the two-deadline cycle — sequencing evidence building, the September 9, 2026 submission gate, author-response windows, the December 21 notification, Major Revision resubmission six weeks later, artifact evaluation, and the April 2027 conference in Crete, with owners per risk.
   1k repo stars
10. ▌
    Atc Review Process · brycewang-stanford

    Use when reasoning about how an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) submission is evaluated — the two-round extended-abstract model, the round-one gate by two reviewers, the round-two read by 3-4 reviewers, double-blind reviewing, rebuttal, conditional acceptance with shepherding, and how ATC differs from OSDI/SOSP/NSDI.
    1k repo stars
11. ▌
    Cav Review Process · brycewang-stanford

    Use when reasoning about how a CAV (Computer Aided Verification) submission is evaluated, covering the two-stage reviewing process (two reviews then an early-reject filter, then two more reviews with a rebuttal), the partial double-anonymity by category, the accept/reject outcome, the optional non-conditional artifact evaluation, and how CAV differs from TACAS and FMCAD.
    1k repo stars
12. ▌
    Cell Star Methods · brycewang-stanford

    Use to build Cell's mandatory STAR Methods — the Key Resources Table, the three Resource Availability subsections, Experimental Model and Subject Details, Method Details, and Quantification and Statistical Analysis, in the exact required order.
    1k repo stars
13. ▌
    Chi Review Process · brycewang-stanford

    Use when interpreting the ACM CHI Papers review pipeline — 1AC and 2AC roles, the A/ARR/RR/RRX/X recommendation scale, desk-reject and rubric-based assisted desk-reject screening, the revise-and-resubmit threshold, round-2 PC decisions — and what each stage means for authors.
    1k repo stars
14. ▌
    Cikm Camera Ready · brycewang-stanford

    Use when turning an accepted CIKM paper into its ACM proceedings version inside the short notification-to-camera-ready window, covering de-anonymization, the e-rights and TAPS pipeline into the ACM Digital Library, CCS concepts and metadata, GenAI-disclosure retention, artifact link publication, and Rome presentation logistics.
    1k repo stars
15. ▌
    Cikm Related Work · brycewang-stanford

    Use when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding against misattributing SIGIR/KDD/ICDM classics to CIKM, and handling preprints under the arXiv-declaration and dual-submission rules.
    1k repo stars
16. ▌
    Colm Camera Ready · brycewang-stanford

    Use when converting a COLM acceptance into the final paper — the August 7 camera-ready deadline in 2026, de-anonymization and the one-page acknowledgments allowance, folding rebuttal commitments into the text, publishing on OpenReview, releasing artifacts publicly, and planning the October conference in San Francisco.
    1k repo stars
17. ▌
    Colm Related Work · brycewang-stanford

    Use when positioning a COLM paper inside the fastest-moving literature in ML — triaging arXiv-heavy citations, handling concurrent work fairly, citing model and dataset artifacts correctly, distinguishing COLM's three-edition archive from adjacent venues' archives, and keeping self-citation double-blind safe.
    1k repo stars
18. ▌
    Colt Camera Ready · brycewang-stanford

    Use when converting an accepted COLT (Conference on Learning Theory) paper into its PMLR proceedings version, covering de-anonymization, acknowledgements and funding restoration, appendix consolidation into the archival PDF, PMLR volume metadata and BibTeX hygiene, rebuttal-promised edits, and presentation logistics.
    1k repo stars
19. ▌
    Colt Related Work · brycewang-stanford

    Use when positioning a COLT (Conference on Learning Theory) submission against prior bounds and models — building the known-versus-new comparison across COLT/ALT lineage, STOC/FOCS, NeurIPS-and-ICML theory tracks, statistics journals, and arXiv concurrency, while respecting anonymity and the parallel-submission rules.
    1k repo stars
20. ▌
    Conext Workflow · brycewang-stanford

    Use when planning an ACM CoNEXT campaign backward from a deadline, covering the choice between the December and June submission cycles, the mandatory registration step, the one-shot major-revision window, the reproducibility badge opt-in due at submission, PACMNET camera-ready, and presentation — all on CoNEXT's distinctive two-cycles-per-year calendar.
    1k repo stars
21. ▌
    Corl Camera Ready · brycewang-stanford

    Use when converting an accepted CoRL paper into its final form — the 9-page camera-ready main text with the extra page for review feedback, the final-mode corl LaTeX template, appendix merged into one PDF, de-anonymization, external hosting for videos because PMLR accepts none, and the October deadline into the PMLR volume.
    1k repo stars
22. ▌
    Corl Related Work · brycewang-stanford

    Use when positioning a CoRL paper against the literature — the robot-learning lineage across CoRL/RSS/ICRA, the ML-methods stream from NeurIPS/ICLR/ICML, the fast-moving VLA and foundation-model wave, classical robotics baselines, concurrent arXiv work, and PMLR citation hygiene including the year-offset trap.
    1k repo stars
23. ▌
    Cscw Camera Ready · brycewang-stanford

    Use when a CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions, deanonymizing text and artifacts, ACM journal e-rights and TAPS steps, issue assignment, and the separate track of presenting at the next CSCW conference.
    1k repo stars
24. ▌
    Cscw Related Work · brycewang-stanford

    Use when positioning a CSCW paper's related work — engaging the venue's own concept lineage, the PACMHCI-era literature, neighboring HCI venues, and the social sciences CSCW borrows from, with era-correct citations and anonymity-safe self-references for journal-model review.
    1k repo stars
25. ▌
    Cvpr Camera Ready · brycewang-stanford

    Use when preparing the final version of an accepted CVPR paper, covering de-anonymization, the dataset-release-by-camera-ready obligation, CVF open access versus the IEEE Xplore version of record, oral/highlight/poster preparation at conference scale, and arXiv/preprint synchronization after acceptance.
    1k repo stars
26. ▌
    Cvpr Related Work · brycewang-stanford

    Use when building the related-work section and positioning for a CVPR paper, covering literature that moves at arXiv speed, concurrent-work etiquette, the CVPR/ICCV/ECCV sibling triangle, double-blind self-citation, verifying that cited "CVPR papers" are actually CVPR papers, and defining deltas against the true nearest neighbors.
    1k repo stars
27. ▌
    Dac Review Process · brycewang-stanford

    Use when reasoning about how an ACM/IEEE Design Automation Conference (DAC) Research Manuscript is evaluated, covering double-blind TPC review, the novelty-plus-QoR decision criteria, program-committee discussion, the accept/reject (no major-revision) outcome, the ~20-25% selectivity, and how DAC's industry-facing, single-shot process differs from the architecture venues' rebuttal-and-revision cycles.
    1k repo stars
28. ▌
    Eacl Camera Ready · brycewang-stanford

    Use when preparing an EACL or Findings-of-ACL-EACL camera-ready after commitment acceptance, covering the extra content page, de-anonymization, AI-assistance disclosure, satisfying the meta-review's required changes, ACL Anthology metadata and CC BY licensing, registration and presentation obligations, and the public artifact release.
    1k repo stars
29. ▌
    Eacl Related Work · brycewang-stanford

    Use when positioning an EACL paper against fast-moving NLP literature, covering ACL-Anthology-first citation, correct Findings attribution, handling concurrent preprints fairly, freshness sweeps across recent *ACL rounds and European venues like LREC-COLING, and framing related work as a contrastive argument rather than a list.
    1k repo stars
30. ▌
    Ecai Related Work · brycewang-stanford

    Use when writing the ECAI related-work section — covering the relevant general-AI lanes (symbolic, learning, multi-agent, application) for a broad reviewer pool, writing delta-first positioning, keeping self-citations double-blind, and doing it within a tight reference budget (1 page standalone / 2 pages in IJCAI-ECAI 2026).
    1k repo stars
31. ▌
    Eccv Camera Ready · brycewang-stanford

    Use when preparing an accepted ECCV paper for Springer LNCS publication — the enlarged final page budget, Springer author kit and licensing, the June 30 AoE camera-ready cutoff in 2026, registration as a publication condition, ECVA open-access mirroring about four weeks before the conference, and arXiv synchronization.
    1k repo stars
32. ▌
    Eccv Related Work · brycewang-stanford

    Use when positioning an ECCV submission in the literature — covering the two intervening CVPR/ICCV cycles since the last ECCV, March-deadline concurrent-work conventions, the no-self-repo citation rule, Springer-vs-CVF venue attribution hygiene, and turning a numbered LNCS bibliography into an argument.
    1k repo stars
33. ▌
    Edbt Camera Ready · brycewang-stanford

    Use when preparing an accepted EDBT paper for its OpenProceedings camera-ready, covering the host/OpenProceedings LaTeX template, the CC-BY-NC-ND open-access license and copyright form, ISBN/volume metadata, integrating reviewer-required changes without scope creep, permanentizing artifact links, and the presentation obligation.
    1k repo stars
34. ▌
    Edbt Related Work · brycewang-stanford

    Use when positioning an EDBT submission against the data-management literature across SIGMOD, VLDB/PVLDB, ICDE, EDBT, the co-located ICDT, and the database journals (VLDBJ, TODS, TKDE), writing delta-first contrast rather than a citation catalog, and handling the 12-month EDBT resubmission ban, preprints, and prior-version overlap.
    1k repo stars
35. ▌
    Emnlp Submission · brycewang-stanford

    Use when auditing an EMNLP submission before the ACL Rolling Review deadline, covering ACL-template compliance, the 8-page long / 4-page short caps, the mandatory Limitations section, the Responsible NLP checklist and its desk-reject enforcement, anonymization without an anonymity period, venue preference, and reciprocal-reviewing duties.
    1k repo stars
36. ▌
    Facct Submission · brycewang-stanford

    Use when auditing an ACM FAccT submission for OpenReview readiness — the mandatory abstract-registration gate with focus-area selection, the acmart anonymous/review PDF, the 14-page (+1 endmatter) budget, mutual anonymity, the required Generative AI Usage Statement and optional ethics/adverse-impacts statements, archival vs non-archival choice, and desk-reject triage before the deadline.
    1k repo stars
37. ▌
    Fast Camera Ready · brycewang-stanford

    Use when preparing an accepted USENIX FAST paper for its open-access camera-ready, covering de-anonymization, the USENIX two-column template and the larger camera-ready page allowance, integrating shepherd- or revision-required changes without scope creep, permanentizing trace and code availability, adding the artifact appendix and USENIX badges, and meeting the final-files deadline.
    1k repo stars
38. ▌
    Focs Camera Ready · brycewang-stanford

    Use when converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization steps, the public arXiv/ECCC full version the CFP expects, the New York talk, and award-eligibility hygiene.
    1k repo stars
39. ▌
    Focs Related Work · brycewang-stanford

    Use when building the related-work and citation apparatus of a FOCS (IEEE Symposium on Foundations of Computer Science) paper — tracing result lineages across the FOCS/STOC record, citing arXiv/ECCC full versions with version pins, handling concurrent preprints, and keeping self-citation double-blind-safe.
    1k repo stars
40. ▌
    Fse Review Process · brycewang-stanford

    Use when reasoning about how an ESEC/FSE research submission is evaluated, covering double-anonymous "heavy" review, the at-least-three-reviewer PC model, the Accept / Major Revision / Reject decision categories, the journal-style revise-and-resubmit round of PACMSE, and how FSE's process differs from ICSE's cycles and ISSTA's rounds.
    1k repo stars
41. ▌
    Hri Review Process · brycewang-stanford

    Use to understand and navigate the ACM/IEEE HRI full-paper review pipeline — the initial desk check and track assignment, the 1AC/2AC plus three external reviewers, the double-blind two-phase model, the author rebuttal, the online reviewer discussion, the program-committee meeting, and the per-track subcommittees — and to see where author leverage exists.
    1k repo stars
42. ▌
    Icalp Submission · brycewang-stanford

    Use when auditing an ICALP (EATCS) Track A or Track B submission for HotCRP readiness, covering the correct-track submission server, abstract registration before the full-paper deadline, the 15-page extended-abstract page budget with a clearly labelled appendix / full version, lightweight double-blind anonymity, the no-simultaneous-submission rule, and the single annual February AoE cutoff.
    1k repo stars
43. ▌
    Icassp Workflow · brycewang-stanford

    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.
    1k repo stars
44. ▌
    Iccv Camera Ready · brycewang-stanford

    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.
    1k repo stars
45. ▌
    Iccv Related Work · brycewang-stanford

    Use when positioning an ICCV paper against the literature, covering the intervening-cycle problem of citing a CVPR and an ECCV that happened since the last ICCV, concurrent-preprint etiquette around the March deadline, double-blind self-reference and the do-not-cite-your-repo rule, and venue-attribution hygiene across the vision big three.
    1k repo stars
46. ▌
    Icde Related Work · brycewang-stanford

    Use when positioning an IEEE ICDE submission against the database canon and neighboring venues, running a reinvention audit across SIGMOD, VLDB, EDBT, and shipping systems, handling two-round concurrency, distinguishing engineering delta from genuine novelty, and covering both the literature and production systems an ICDE reviewer expects.
    1k repo stars
47. ▌
    Icdm Camera Ready · brycewang-stanford

    Use when preparing the ICDM (IEEE International Conference on Data Mining) camera-ready after acceptance - IEEE final formatting and eCopyright, de-anonymizing a triple-blind paper, handling an Accept-as-Short outcome by compressing to short-paper length, registering for in-person presentation, and getting the paper into IEEE Xplore.
    1k repo stars
48. ▌
    Icdm Related Work · brycewang-stanford

    Use when positioning an ICDM (IEEE International Conference on Data Mining) paper's related work - lineage against prior ICDM editions and IEEE data-mining neighbors, the mechanism-contrast novelty sentence, avoiding KDD/SDM/CIKM/WSDM venue misattribution, and citing your own prior work in the third person so the section stays triple-blind-safe.
    1k repo stars
49. ▌
    Icdt Camera Ready · brycewang-stanford

    Use when preparing the final LIPIcs camera-ready for an accepted ICDT (International Conference on Database Theory) paper — the lipics-v2021 final document, mandatory ACM CCS concepts and keywords, author ORCIDs, de-anonymization, complete proofs and the full-version link, CC-BY licensing, and passing the Dagstuhl/DROPS production checks that mint the DOI.
    1k repo stars
50. ▌
    Icdt Related Work · brycewang-stanford

    Use when positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and complexity, delta-first positioning against the nearest prior theorem, honest treatment of overlapping bounds, and keeping self-citations anonymous under the since-2024 rule.
    1k repo stars
51. ▌
    Iclr Camera Ready · brycewang-stanford

    Use when preparing an accepted ICLR paper for camera-ready submission, OpenReview metadata, poster instructions, slide deck, project page, video, and publication logistics. Use when de-anonymizing the final PDF, folding in promised discussion-period fixes, confirming the camera-ready page allowance for the current cycle, or assembling poster and presentation assets for ICLR's poster-heavy program.
    1k repo stars
52. ▌
    Iclr Related Work · brycewang-stanford

    Use when positioning an ICLR paper against prior work, concurrent OpenReview submissions, arXiv papers, benchmark lineages, and adjacent learning-representation claims. Use when a reviewer cites a paper you missed, when a public comment disputes your novelty, or when separating "shares a component with" from "solves the same representation-learning problem" so the claim survives permanent public scrutiny.
    1k repo stars
53. ▌
    Icml Camera Ready · brycewang-stanford

    Use when preparing accepted ICML papers for camera-ready upload, PMLR agreement, public OpenReview record, lay summary, conflict disclosure, registration/presentation choices, format checker, and post-conference revision.
    1k repo stars
54. ▌
    Icml Related Work · brycewang-stanford

    Use when positioning an ICML submission against close ML literature, concurrent ICML submissions, recent public papers, workshop papers, ICLR/AISTATS/NeurIPS neighbors, and prior work under double-blind constraints.
    1k repo stars
55. ▌
    Icra Camera Ready · brycewang-stanford

    Use when converting an accepted ICRA paper into its final form — the 8-page total limit including references, de-anonymization after double-anonymous review, PaperPlaza final upload and PDF compliance, IEEE electronic copyright transfer, final video, author registration requirements, and IEEE Xplore publication.
    1k repo stars
56. ▌
    Icra Related Work · brycewang-stanford

    Use when building or auditing the related-work section of an ICRA paper — covering the conference's own recent proceedings plus IROS, RSS, CoRL, RA-L, and T-RO lanes, handling arXiv-only robotics work, citing your own platform papers under ICRA's double-anonymous rules, and positioning against commercial systems.
    1k repo stars
57. ▌
    Icse Camera Ready · brycewang-stanford

    Use when converting an accepted ICSE research-track paper into its final published form, covering the extra camera-ready page, de-anonymization order, finalizing the Data Availability section with archival DOIs, IEEE-template production checks, and conference-presentation obligations to verify.
    1k repo stars
58. ▌
    Icse Related Work · brycewang-stanford

    Use when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and dblp across the flagship venues, staying current in fast-moving areas like LLM4SE, and keeping self-citations double-anonymous.
    1k repo stars
59. ▌
    Icsme Submission · brycewang-stanford

    Use when auditing an IEEE ICSME research-track submission for EasyChair readiness, covering the abstract-then-paper two-step deadline, the IEEEtran two-column 10+2 page budget, double-anonymous review, the open-science data-availability expectation, and desk-reject triage before the AoE cutoff.
    1k repo stars
60. ▌
    Ijcai Submission · brycewang-stanford

    Use when auditing an IJCAI or IJCAI-ECAI main-track submission for Chairing Tool readiness, abstract and author-information deadlines, page limits, double-blind anonymity, supplementary files, reproducibility, resubmission information, author limits, dual-submission policy, and LLM-use policy.
    1k repo stars
61. ▌
    Imc Review Process · brycewang-stanford

    Use when reasoning about how an ACM IMC submission is evaluated, covering double-blind multi-round review, the Accept / One-Shot-Revision / Reject decision categories, the reviewer-champion rule and bounded action points, early rejection of consensus-reject papers, shepherding for artifact availability, and how IMC's two-deadline model differs from SIGCOMM/NSDI cycles.
    1k repo stars
62. ▌
    Ipsn Camera Ready · brycewang-stanford

    Use when preparing an accepted IPSN-lineage paper for camera-ready, covering de-anonymization, the ACM Primary Article Template and the dual ACM/IEEE metadata (CCS concepts, ORCID, DOI, IEEE PDF eXpress/e-copyright), integrating required changes without scope creep, permanentizing dataset/firmware links, and the artifact-award handoff.
    1k repo stars
63. ▌
    Ipsn Related Work · brycewang-stanford

    Use when positioning an IPSN-lineage submission against the sensor-networks and information-processing literature (IPSN, SenSys, MobiCom, MobiSys, INFOCOM, and signal-processing venues), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind, and handling concurrent, preprint, and prior-version overlap.
    1k repo stars
64. ▌
    Iros Camera Ready · brycewang-stanford

    Use when preparing an accepted IROS paper for IEEE Xplore camera-ready — de-anonymization from the double-anonymous cycle, integrating the meta-review, the IEEE electronic copyright form (eCF), the July final-paper deadline, registration and in-person presentation, and the public artifact release anonymity had blocked.
    1k repo stars
65. ▌
    Iros Related Work · brycewang-stanford

    Use when positioning an IROS submission against robotics-systems literature across ICRA, IROS, RSS, CoRL, RA-L, and T-RO, covering the lanes embodied-systems reviewers check, concurrent arXiv work, prior-version overlap, IEEE Xplore archival status, and keeping self-citations anonymous under the double-anonymous cycle.
    1k repo stars
66. ▌
    Isca Camera Ready · brycewang-stanford

    Use when converting an accepted ISCA paper into its published form — de-anonymizing authors, acknowledgments, and artifact links; satisfying the edition's publisher workflow under the alternating ACM/IEEE arrangement; integrating shepherd requirements and badges; and preparing the June talk and attendance logistics.
    1k repo stars
67. ▌
    Isca Related Work · brycewang-stanford

    Use when positioning an ISCA submission against prior art — covering five decades of architecture literature across ACM DL, IEEE Xplore, and dblp, differentiating by mechanism rather than metric, handling self-citations and arXiv preprints under double-blind rules, and exploiting ISCA's unlimited reference pages.
    1k repo stars
68. ▌
    Issta Submission · brycewang-stanford

    Use when auditing an ISSTA submission for HotCRP readiness, the 18-page (excluding references) limit, ACM sigconf plus review and anonymous formatting, double-anonymous integrity, the January deadline, artifact intent, track choice among research/experience/replicability, and desk-reject triggers before the phase-one upload.
    1k repo stars
69. ▌
    Itcs Camera Ready · brycewang-stanford

    Use when preparing an accepted ITCS paper for open-access publication in LIPIcs — switching to the lipics-v2021 document class, de-anonymizing, completing LIPIcs metadata (ACM CCS, keywords, funding), folding in reviewer-noted fixes, and passing the Schloss Dagstuhl production checks.
    1k repo stars
70. ▌
    Itcs Related Work · brycewang-stanford

    Use when positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new, covering the right STOC/FOCS/SODA/CCC/TCC lanes, and staying honest under lightweight double-blind where the reference list is not anonymized.
    1k repo stars
71. ▌
    Jama Cover Letter · brycewang-stanford

    Use when drafting the editor-facing cover letter that pitches a JAMA manuscript's general medical importance and confirms compliance. Frames the pitch and declarations; it does NOT write the manuscript or the abstract.
    1k repo stars
72. ▌
    Jama Study Design · brycewang-stanford

    Use when locking the study design and internal-validity safeguards for a JAMA clinical manuscript (RCT, cohort, diagnostic, or systematic review). Strengthens design choices; it does NOT pick the reporting checklist or run the statistics.
    1k repo stars
73. ▌
    Lancet Abstract · brycewang-stanford

    Use to write The Lancet's structured abstract — ≤300 words under the exact headings Background, Methods, Findings, Interpretation, Funding — leading with the clinical question, reporting the primary outcome with effect size and 95% CI, citing the registration number, and naming the funder.
    1k repo stars
74. ▌
    Lancet Rebuttal · brycewang-stanford

    Use after Lancet reviews arrive (including the statistical reviewer and the editor's letter) to triage the decision, answer statistical and clinical comments, and draft a point-by-point response that quotes the reviewer, gives evidence, quotes the revised manuscript text, and keeps causal language cautious. Do not run before the main text is actually revised.
    1k repo stars
75. ▌
    Lancet Workflow · brycewang-stanford

    Use when deciding which lancet-* sub-skill to invoke next, or when sequencing a clinical or global-health manuscript from significance test through reviewer rebuttal for The Lancet. Routes — it does not replace — the specialized skills.
    1k repo stars
76. ▌
    Micro Submission · brycewang-stanford

    Use when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the abstract-registration gate a week before the paper, minimum 9pt fonts, mandatory page numbers, all-author reference entries, and MICRO's visual-plus-automated format inspection.
    1k repo stars
77. ▌
    Mlsys Submission · brycewang-stanford

    Use when auditing an MLSys submission for OpenReview readiness, covering the two-column 10-page body excluding references, the separate appendix upload, double-blind rules that still permit arXiv posting, research-versus-industrial track requirements, dual-submission exceptions, style-kit compliance, and desk-reject triage before the deadline.
    1k repo stars
78. ▌
    Naacl Submission · brycewang-stanford

    Use when a paper aimed at NAACL is about to be uploaded to an ACL Rolling Review cycle — verifying that the chosen cycle can still reach the next NAACL edition, that the PDF passes ARR's format and anonymization gates, and that every declaration on the OpenReview form survives a desk-reject audit.
    1k repo stars
79. ▌
    Ndss Camera Ready · brycewang-stanford

    Use when converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions, de-anonymizing, restoring disclosure specifics, adding earned artifact badges, and meeting the Internet Society proceedings and camera-ready requirements by the January deadline.
    1k repo stars
80. ▌
    Ndss Related Work · brycewang-stanford

    Use when positioning an NDSS submission against prior literature — sweeping the security big four plus the specialist venues, writing precise deltas, verifying every citation against NDSS's open proceedings and dblp, and keeping self-reference double-blind.
    1k repo stars
81. ▌
    Nejm Study Design · brycewang-stanford

    Use to confirm study-design rigor and the mandatory prospective trial registration, protocol, and statistical analysis plan before writing up a clinical study for NEJM. Surfaces registration problems early — they cannot be fixed retroactively.
    1k repo stars
82. ▌
    Nsdi Camera Ready · brycewang-stanford

    Use when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community Award eligibility, designating the presenter, and landing in USENIX's open-access proceedings for the May symposium.
    1k repo stars
83. ▌
    Nsdi Related Work · brycewang-stanford

    Use when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current edition, verifying venues against dblp and open-access USENIX proceedings, and handling self-citations and concurrent submissions under double-blind rules.
    1k repo stars
84. ▌
    Oopsla Workflow · brycewang-stanford

    Use when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or OOPSLA2 PACMPL issue, scheduling artifact evaluation, and landing the SPLASH talk, with dates re-anchored to the live cycle.
    1k repo stars
85. ▌
    Osdi Camera Ready · brycewang-stanford

    Use when converting an OSDI acceptance into the published paper — the June final-paper deadline, expansion to 14 pages plus appendices, the two-page Artifact Appendix, de-anonymization and restored acknowledgments, USENIX open-access publication from day one, and presenter obligations in Seattle.
    1k repo stars
86. ▌
    Osdi Related Work · brycewang-stanford

    Use when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access proceedings and dblp, and citing your own precursors without breaking the renamed-system anonymity rule.
    1k repo stars
87. ▌
    Percom Workflow · brycewang-stanford

    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.
    1k repo stars
88. ▌
    Pldi Camera Ready · brycewang-stanford

    Use when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every author-response commitment, and coordinating the Zenodo artifact and June conference presentation.
    1k repo stars
89. ▌
    Pldi Related Work · brycewang-stanford

    Use when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles, citing PACMPL-era papers in journal form, and verifying every venue attribution on dblp before it ships.
    1k repo stars
90. ▌
    Pnas Significance · brycewang-stanford

    Use to write the mandatory PNAS Significance Statement — ≤120 words, written so an educated reader outside the field (down to an undergraduate) understands why the work matters. Distinct from the abstract. The highest-value PNAS-specific artifact.
    1k repo stars
91. ▌
    Podc Camera Ready · brycewang-stanford

    Use when preparing an accepted ACM PODC paper for the proceedings — de-anonymizing after lightweight double-blind, compressing to the 10-page two-column ACM proceedings format without losing the proof map, completing ACM rights/eRights metadata and CCS concepts, and posting the synchronized full version with all proofs to arXiv.
    1k repo stars
92. ▌
    Podc Related Work · brycewang-stanford

    Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing journals), writing a model-and-bound-precise delta over prior results, distinguishing your model from neighboring ones, and keeping self-citation safe under lightweight double-blind review.
    1k repo stars
93. ▌
    Pods Camera Ready · brycewang-stanford

    Use when preparing an accepted ACM PODS paper for its PACMMOD-track camera-ready, covering de-anonymization, the final acmsmall format and PACMMOD journal metadata (DOI, ORCID, CCS concepts), integrating shepherd-required revision items without overclaiming, posting and DOI-linking the arXiv full version, and confirming registration and presentation.
    1k repo stars
94. ▌
    Popl Camera Ready · brycewang-stanford

    Use when a POPL paper is conditionally accepted — planning the mandatory revision the Review Committee must approve, de-anonymizing for PACMPL Issue POPL, handling ORCID/open-access/APC steps on the ACM side, syncing the paper with its proof artifact, and preparing the January talk.
    1k repo stars
95. ▌
    Popl Related Work · brycewang-stanford

    Use when positioning a POPL paper in the semantics, type-systems, and verification literature — stating per-line technical deltas against the nearest formal systems, covering the PACMPL family and LICS/CAV/CPP/TOPLAS neighbors, citing PACMPL-era papers in journal form, and dblp-verifying every classic before it is attributed to POPL.
    1k repo stars
96. ▌
    Ppopp Submission · brycewang-stanford

    Use when auditing a PPoPP research-paper submission for HotCRP readiness, covering the two-column acmart sigplan template, the 10-page text+figures budget with unlimited references, the 100-400 word abstract, double-blind anonymity for parallel-systems work, conflict declaration against the PC and External Review Committee, and desk-reject triage before the AoE cutoff.
    1k repo stars
97. ▌
    Recsys Workflow · brycewang-stanford

    Use when planning an ACM RecSys project timeline from venue fit through abstract, full paper, the anonymous repository, rebuttal, decision, ACM camera-ready, registration, and presentation, with backward-planning offsets for an offline-evaluation recommender paper and per-track date awareness (Main, Reproducibility, Industry, Resource, R&P Notes).
    1k repo stars
98. ▌
    Sci Statistics · brycewang-stanford

    Use to enforce Science's statistics and reproducibility reporting — n and replication, test choice and assumptions, effect sizes with uncertainty, multiple-comparison control, randomization/blinding, and pre-registration where relevant.
    1k repo stars
99. ▌
    Sci Submission · brycewang-stanford bundle

    Use as the final preflight before submitting to Science (AAAS) — a complete checklist across significance, format, figures, statistics, data availability, references, and required submission files, so nothing that triggers an editorial bounce is left unresolved. Bundles ready-to-fill templates.
    1k repo stars
100. ▌
     Sensys Workflow · brycewang-stanford

     Use when planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds, backward-scheduling so energy campaigns and long-term deployments finish before freeze, budgeting time for the resubmission-with-revision path, and sequencing fit, building, writing, and submission.
     1k repo stars