← 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. ▌
   Nejm Citation · brycewang-stanford

   Use to convert references to NEJM's Vancouver / ICMJE numbered style — numbered in order of appearance, limited author lists then et al., NLM journal abbreviations, and a capped reference count. Late-stage style pass.
   1k repo stars
2. ▌
   Nejm Rebuttal · brycewang-stanford

   Use after NEJM reviews arrive — often including a dedicated statistical reviewer and an editor letter — to triage the decision, answer statistical comments rigorously, and draft a point-by-point response that quotes each comment, the response, and the revised manuscript text. Do not run before the main text is actually revised.
   1k repo stars
3. ▌
   Nejm Workflow · brycewang-stanford

   Use when deciding which nejm-* sub-skill to invoke next, or when sequencing a clinical manuscript from significance test through response to reviewers for The New England Journal of Medicine. Routes — it does not replace — the specialized skills.
   1k repo stars
4. ▌
   Nsdi Workflow · brycewang-stanford

   Use when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.
   1k repo stars
5. ▌
   Osdi Workflow · brycewang-stanford

   Use when planning or managing a full OSDI cycle — the December title-registration and submission deadlines on HotCRP, the silent no-rebuttal review window, March notification, the May artifact deadline, June shepherded final papers, and the July conference — including rejection retargeting to SOSP or NSDI.
   1k repo stars
6. ▌
   Pldi Workflow · brycewang-stanford

   Use when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.
   1k repo stars
7. ▌
   Pmla Workflow · brycewang-stanford

   Use as the entry point for any PMLA (Publications of the Modern Language Association) manuscript. Routes to the right PMLA sub-skill based on where you are in the lifecycle and which venue fits — a regular blind-reviewed article or a special feature (Theories and Methodologies, The Changing Profession, Criticism in Translation, Little-known Documents). It dispatches; it does not draft content.
   1k repo stars
8. ▌
   Pnas Abstract · brycewang-stanford

   Use to write the PNAS abstract — a single self-contained paragraph of ~250 words, quantified and accessible to a broad scientific audience. Distinguishes the abstract (what/how/found, for scientists) from the Significance Statement (why-it-matters, for everyone). Late-stage polish.
   1k repo stars
9. ▌
   Pnas Citation · brycewang-stanford

   Use to convert references to PNAS's numbered citation style — cited in order of appearance, a numbered reference list, full author lists, abbreviated journal titles. Provides formats for article/book/chapter/dataset/preprint and an author-date → PNAS conversion table. Late-stage style pass.
   1k repo stars
10. ▌
    Pnas Rebuttal · brycewang-stanford

    Use after PNAS reviews arrive to triage the decision, prioritize experiments, and draft a point-by-point response that is respectful, evidence-led, and honest about limits. Do not run before the main text is actually revised.
    1k repo stars
11. ▌
    Pnas Workflow · brycewang-stanford

    Use when deciding which pnas-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for PNAS (Proceedings of the National Academy of Sciences). Routes — it does not replace — the specialized skills.
    1k repo stars
12. ▌
    Podc Workflow · brycewang-stanford

    Use when planning an ACM PODC campaign end to end — running the single annual cycle backward from the February deadline through abstract registration, lightweight double-blind review, the late-April notification, the May camera-ready, and the arXiv full version — and coordinating the regular-paper-vs-Brief-Announcement decision along the way.
    1k repo stars
13. ▌
    Pods Workflow · brycewang-stanford

    Use when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour rebuttal, the accept/reject/revision decision and shepherded revision round, PACMMOD-track publication, the arXiv full version, and presentation — with backward-planning offsets for a theory paper and honest handling of cycle choice.
    1k repo stars
14. ▌
    Popl Workflow · brycewang-stanford

    Use when planning a POPL campaign calendar — backward-scheduling theory and mechanization from the July deadline, riding the October notification into the conditional-acceptance revision and artifact evaluation, landing the January conference, and retargeting across the SIGPLAN/PACMPL deadline wheel if July slips.
    1k repo stars
15. ▌
    Rss Submission · brycewang-stanford

    RSS Submission
    1k repo stars
16. ▌
    Socc Workflow · brycewang-stanford

    Use when planning an ACM SoCC project timeline from venue fit through the two-round abstract+paper deadlines, the rebuttal, notification, camera-ready, and presentation, with backward-planning offsets for a cloud-systems measurement paper and honest handling of the two-rounds-per-year cadence and the no-cross-round-resubmission rule.
    1k repo stars
17. ▌
    Soda Workflow · brycewang-stanford

    Use when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between STOC and FOCS deadlines, the September rebuttal and October decision, satellite deadlines (ALENEX, SOSA), and the January conference.
    1k repo stars
18. ▌
    Sosp Workflow · brycewang-stanford

    Use when planning a SOSP campaign across the annual cycle — back-scheduling from the spring abstract and paper deadlines, running the summer response and July notification, stacking the August camera-ready with artifact evaluation, and retargeting rejections across the SOSP/OSDI/EuroSys circuit.
    1k repo stars
19. ▌
    Stoc Workflow · brycewang-stanford

    Use when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.
    1k repo stars
20. ▌
    Uai Submission · brycewang-stanford

    Use when auditing a UAI submission for OpenReview readiness, covering the February paper deadline, the 8-page main part with unlimited appendices in one PDF, the 15 MB file cap, the optional 50 MB supplementary ZIP, double-blind rules, the reviewer-volunteer agreement, dual-submission checks, and desk-reject triage before upload.
    1k repo stars
21. ▌
    Uist Workflow · brycewang-stanford

    Use when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional acceptance, the July camera-ready, adjunct-track parallel lanes, and the November conference — with owners and risk buffers.
    1k repo stars
22. ▌
    Vis Submission · brycewang-stanford

    Use when auditing an IEEE VIS full-paper submission for PCS readiness, covering the abstract-then-paper two-deadline structure under the VGTC society, the IEEE VGTC/TVCG 9+2 page budget, author-optional double-blind anonymization, the supplemental-material one-week window, and desk-reject triage before the AoE cutoff for a paper that will publish in IEEE TVCG.
    1k repo stars
23. ▌
    Vldb Workflow · brycewang-stanford

    Use when planning a VLDB project on the PVLDB rolling calendar, covering month-picking strategy, the volume-to-conference mapping and acceptance cutoff, budgeting a possible three-month revision, coordinating author caps across a group, and backward planning from the 25th-abstract / 1st-paper rhythm.
    1k repo stars
24. ▌
    Wacv Workflow · brycewang-stanford

    Use when planning a WACV campaign calendar across the two-round model, from track and round choice through the Round 1 submission, rebuttal, and Accept/Revise-and-Resubmit/Reject decision, into the Round 2 revision and decision, camera-ready, and the winter conference — with the branch points that a single-deadline plan misses.
    1k repo stars
25. ▌
    Wsdm Workflow · brycewang-stanford

    Use when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference, backward milestone planning, the September short-paper fallback, alternate entrances (demos, WSDM Cup, doctoral consortium), and coordination with sibling-venue deadlines.
    1k repo stars
26. ▌
    Acl Experiments · brycewang-stanford

    Use when designing or auditing experiments for an ACL paper, covering tuned LLM baselines, multi-dataset and multilingual evaluation, statistical significance and variance, human evaluation with agreement reporting, contamination and prompt-sensitivity controls, ablations, and error-analysis expectations in NLP reviewing.
    1k repo stars
27. ▌
    Ase Experiments · brycewang-stanford

    Use when designing or auditing the evaluation of an ASE (IEEE/ACM Automated Software Engineering) paper, covering real subject systems, fair runnable tool baselines, task-matched effectiveness metrics, ablations that isolate a learned component, oracle and correctness validation, contamination-aware LLM handling, and provenance for mining.
    1k repo stars
28. ▌
    Cell Fit · brycewang-stanford

    Use when triaging a study before any writing — stress-tests whether it clears Cell's bar (a complete, mechanistic, hypothesis-driven story with multiple converging lines of evidence) or belongs at a sibling. Use this first to decide Cell vs Molecular Cell vs Cell Reports vs Cell Reports Medicine before investing in framing or figures.
    1k repo stars
29. ▌
    Nejm Fit · brycewang-stanford

    Use this first, before any writing, to stress-test whether a clinical study clears NEJM's bar — practice-changing clinical impact, methodological rigor, and generalizability. Decides NEJM vs Lancet/JAMA vs a specialty journal.
    1k repo stars
30. ▌
    Pnas Fit · brycewang-stanford

    Use before any writing begins to stress-test whether a result clears PNAS's bar — high quality and broad significance to a general scientific readership — and to make the realistic call between PNAS, Science/Nature, and a specialist field journal.
    1k repo stars
31. ▌
    Cell Data · brycewang-stanford

    Use to build Cell's data and code deposition plan and the Data and Code Availability statement that lives inside STAR Methods Resource Availability — approved repositories, accessions/DOIs at submission, and Cell's three-bullet availability format with Mendeley Data as Elsevier's default.
    1k repo stars
32. ▌
    Pnas Data · brycewang-stanford

    Use to build PNAS's Data Availability Statement and deposition plan — mandatory deposition of data in an approved repository at submission, accession numbers/DOIs, public + archived code, and materials sharing. "Available on request" is not sufficient for primary data.
    1k repo stars
33. ▌
    Pnas Track · brycewang-stanford

    Use to choose the PNAS submission track — Direct Submission (standard, editor-assigned, peer reviewed) vs Contributed Submission (an NAS member communicates their own paper). Covers eligibility, the editor/member role, the discontinued and legacy tracks, and how to pick. Unique to PNAS.
    1k repo stars
34. ▌
    Sci Fit · brycewang-stanford

    Use before any writing to stress-test whether a result clears Science's (AAAS) desk-reject filter — broad significance and general interest across disciplines. Decides Science vs Science Advances vs a specialist journal before you invest in prose.
    1k repo stars
35. ▌
    Acl Workflow · brycewang-stanford

    Use when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR deadline, the review-response-meta-review timeline, commitment decisions, resubmission loops to later cycles, and camera-ready through ACL Anthology publication.
    1k repo stars
36. ▌
    Ase Workflow · brycewang-stanford

    Use when planning an ASE (IEEE/ACM Automated Software Engineering) research-track campaign backward from the deadline, through abstract registration, the double-anonymous submission, the early-rejection gate, rebuttal, the criteria-bound revision round, artifact evaluation, and the camera-ready in both IEEE Xplore and the ACM Digital Library.
    1k repo stars
37. ▌
    Atc Workflow · brycewang-stanford

    Use when planning an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) campaign end to end — running the year backward from the early-June deadline through the two review rounds, the rebuttal, conditional-acceptance shepherding, the post-acceptance artifact evaluation, and the ACM Open Access camera-ready for the November Hong Kong conference.
    1k repo stars
38. ▌
    Cav Workflow · brycewang-stanford

    Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.
    1k repo stars
39. ▌
    Chi Workflow · brycewang-stanford

    Use when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.
    1k repo stars
40. ▌
    Dac Workflow · brycewang-stanford

    Use to plan a full ACM/IEEE Design Automation Conference (DAC) Research-Manuscript campaign backward from the mid-to-late-November manuscript deadline through the two-stage abstract-then-manuscript submission on Softconf, the winter review, the March notification, the April camera-ready and copyright for the ACM Digital Library, and the July conference in Long Beach — with the Engineering-Track and Late-Breaking-Results side calendars.
    1k repo stars
41. ▌
    Fse Workflow · brycewang-stanford

    Use when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE camera-ready, and presentation, with backward-planning offsets for an empirical-SE paper and honest handling of the single-annual-deadline cycle and cycle-hopping.
    1k repo stars
42. ▌
    Hri Workflow · brycewang-stanford

    Use to plan an ACM/IEEE HRI campaign backward from the full-paper deadline through the abstract-then-paper two-step, the rebuttal, the program-committee meeting, camera-ready, and the March conference, coordinating the parallel alt.HRI, Late-Breaking Reports, video, and Student Design deadlines.
    1k repo stars
43. ▌
    Imc Workflow · brycewang-stanford

    Use when planning an ACM IMC campaign end to end, covering the choice between the two annual deadlines, backward planning from the target cutoff, the registration step, the One-Shot-Revision path across deadlines, availability shepherding, the camera-ready and dataset release, and the Replicability Track calendar.
    1k repo stars
44. ▌
    Kdd Workflow · brycewang-stanford

    Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.
    1k repo stars
45. ▌
    Nejm Ethics · brycewang-stanford

    Use to confirm clinical ethics and research-integrity requirements for an NEJM submission — IRB/ethics-committee approval and informed consent per the Declaration of Helsinki, ICMJE conflict-of-interest disclosures and authorship criteria, the role-of-the-funding-source statement, and the ICMJE data-sharing statement.
    1k repo stars
46. ▌
    Rss Workflow · brycewang-stanford

    RSS Workflow
    1k repo stars
47. ▌
    Sci Data · brycewang-stanford

    Use to build Science's data, code, and materials availability — mandatory deposition in approved repositories, accession numbers, a compliant data-availability statement, and materials/reagent sharing.
    1k repo stars
48. ▌
    Uai Workflow · brycewang-stanford

    Use when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the July PMLR camera-ready, and the August conference, as one backward-planned calendar with named owners for anonymity, evidence, and packaging tasks.
    1k repo stars
49. ▌
    Vis Workflow · brycewang-stanford

    Use when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.
    1k repo stars
50. ▌
    Cell Figures · brycewang-stanford

    Use to finalize Cell Press display items — column-width sizing, minimum fonts, RGB, show-the-data with defined error bars/n/replicate type, scale bars, colorblind-safe palettes, multi-panel discipline, stand-alone legends, and image integrity.
    1k repo stars
51. ▌
    Cell Framing · brycewang-stanford

    Use to lock the single narrative arc before drafting — converts a set of correct results into one Cell-shaped story that runs hypothesis → mechanism → significance, not a list of experiments.
    1k repo stars
52. ▌
    Cell Summary · brycewang-stanford

    Use to write Cell's Summary — a single unstructured paragraph of ≤ ~150 words that conveys the complete story, the mechanism, and the broad significance, quantified and readable by a general life-scientist. Late-stage polish.
    1k repo stars
53. ▌
    Cell Writing · brycewang-stanford

    Use to structure a Cell Article and hold its length — Summary, Introduction, Results, Discussion, STAR Methods, figure legends, references — with main-text length and display-item budgets, and Results subheadings driving the single arc.
    1k repo stars
54. ▌
    Lancet Fit · brycewang-stanford

    Use when scoping a project and before any writing, to stress-test whether a study clears The Lancet's bar — clinically or public-health important, globally relevant, and likely to change practice or policy, often with an equity lens. Decides The Lancet vs a Lancet family title vs another general medical journal.
    1k repo stars
55. ▌
    Nejm Writing · brycewang-stanford

    Use to structure and tighten an NEJM Original Article into terse IMRAD — short main text (~2700 words), limited references, claim-first results, and a sober discussion with explicit limitations and calibrated clinical implications. Enforces NEJM's plain, concise house style.
    1k repo stars
56. ▌
    Pnas Figures · brycewang-stanford

    Use to finalize PNAS display items — column-width sizing (~9 / 11.4 / 18 cm), minimum font sizes, show-the-data with n and defined error bars, scale bars, colorblind-safe palettes, legend structure, image integrity, and color-mode notes. Enforces figure rigor before submission.
    1k repo stars
57. ▌
    Pnas Writing · brycewang-stanford

    Use to structure a PNAS main text and hold its length — Title, Significance Statement, Abstract, Introduction, Results, Discussion, in-text Materials and Methods, references — and to choose the required Classification (Biological/Physical/Social Sciences + minor subject) and keywords at submission.
    1k repo stars
58. ▌
    Aaai Workflow · brycewang-stanford

    Use when planning an AAAI project timeline from topic selection through abstract, OpenReview submission, two-phase review, rebuttal, decision, camera-ready, registration, presentation, and public artifact release.
    1k repo stars
59. ▌
    Acl Submission · brycewang-stanford

    Use when auditing an ACL submission before an ACL Rolling Review cycle deadline, covering long/short paper page budgets, the mandatory Limitations section, Responsible NLP checklist, anonymized PDFs and supplements, preprint declarations, dual-submission rules, resubmission linking, and ARR desk-reject triggers on OpenReview.
    1k repo stars
60. ▌
    Ase Submission · brycewang-stanford

    Use when auditing an ASE (IEEE/ACM Automated Software Engineering) research-track submission for HotCRP readiness, covering the ACM acmart sigconf template and the 10+2 page budget, double-anonymous review, the mandatory Data Availability Statement, the early-rejection stage before rebuttal, and desk-reject triage before the deadline.
    1k repo stars
61. ▌
    Atc Submission · brycewang-stanford

    Use when auditing an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) submission for HotCRP readiness — the paired two-page extended abstract plus full paper, the two-column 12/6-page budget, the double-blind anonymity sweep, ACM Open Access publication, and desk-reject triage before the early-June AoE cutoff.
    1k repo stars
62. ▌
    Cav Submission · brycewang-stanford

    Use when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies), the LNCS page limits, the per-category anonymization matrix, the artifact-intent declaration, and desk-reject triage before the AoE paper deadline.
    1k repo stars
63. ▌
    Cell Citation · brycewang-stanford

    Use to convert references to Cell Press author–date style — in-text "(Smith et al., 2021)", an alphabetical reference list by first author with full author lists, journal names spelled out. This is the OPPOSITE of Science's numbered-by-appearance style.
    1k repo stars
64. ▌
    Cell Rebuttal · brycewang-stanford

    Use after Cell reviews arrive to triage the decision, prioritize the (often substantial) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the "completeness" gaps reviewers demand. Do not run before the experiments and revision are actually done.
    1k repo stars