Install in seconds
Install this skill
Copy the command and run it in your terminal. You can review the source before installing.
terminal
git clone https://github.com/brycewang-stanford/Awesome-Journal-Skills

Works with Git. The repository opens in your current directory.

๐Ÿ“…
WritingStata

AAMAS Workflow

by brycewang-stanford

Plan and manage an AAMAS paper submission timeline, including abstract, paper, supplement, rebuttal, camera-ready, and presentation, with track-specific deadlines and backward planning for game-theory experiments.

875 stars106 forksAdded 2026/07/20
academic-researchacademic-writingagent-skillsai-agentsanthropicawesome-listcausal-inferenceclaudeclaude-codeeconometricseconomicsempirical-researchfinancejournalllmmcppeer-reviewreplicationresearch-toolsscholarly-publishing

Documentation

README

AAMAS Workflow

Use this as the project-management skill for an AAMAS submission. Replace every date with the current official timetable and work backward from the OpenReview cutoffs.

AAMAS is a conference owned by IFAAMAS, not a journal: it has no editor-in-chief and no article-processing charge. Each edition is run by rotating General and Program Chairs, the cost model is registration, and accepted papers are published open-access by IFAAMAS. Re-check the current CFP and organization page rather than carrying names or dates forward - as of 2026-07-09 the live target is AAMAS 2027, whose full timetable was not yet confirmable.

Milestones

  • Venue fit: confirm the contribution is genuinely about interacting agents and choose the track (main full paper, extended abstract, AAAI, JAAMAS, Blue Sky, Demo, Competitions).
  • Evidence lock: freeze the game, agent objectives, theorems, opponent sets, experiments, and supplement contents.
  • Abstract deadline: submit the short plain-text abstract, authors, and keywords (main track's abstract is due before the paper).
  • Paper deadline: upload the double-blind PDF and OpenReview fields.
  • Supplement deadline: upload the anonymized zip within the size cap.
  • Rebuttal window: respond to preliminary reviews with anonymous, evidence-anchored text; no new results.
  • Decision: archive reviews, rebuttal, and the submitted version (all become public).
  • Acceptance: prepare the IFAAMAS camera-ready, register, plan the in-person presentation, and release the public artifact.

Backward plan from the paper deadline

Weeks out (heuristic) Game-theory-plus-experiments milestone
8+ Game defined, solution concept fixed, theorems proved
6 Self-play and opponent sets designed against each claim
4 Population runs complete, seeds logged
3 Full draft in AAMAS two-column format
2 Internal mock review by a game-theory-minded reader
1 Anonymity sweep, supplement assembly, deviation-test check
0 Abstract then paper on OpenReview; supplement by its own cutoff

These offsets are planning heuristics only - anchor each to the current official timetable, and remember the AAAI, JAAMAS, and Blue Sky tracks have different deadlines.

Failure modes by stage

  • Theory or the game still moving at week 3 forces last-minute definition edits nobody has re-verified - the classic AAMAS correctness reject in the making.
  • Leaving format conversion to the final week surfaces two-column overflow of game figures late.
  • Skipping the mock review forfeits the only chance to hear "this is really single-agent" from a friend instead of a reviewer.
  • Building the supplement under deadline pressure is how anonymity leaks and missing opponent sets ship.

Coordination notes

  • Assign one named owner for the anonymity sweep and another for the opponent/seed logging; shared ownership is how both slip.
  • Archive the exact submitted PDF, supplement, and any deviation-test harness, since rebuttal replies must quote them precisely and the record goes public.

Output format

[Current stage] idea / experiments / writing / abstract / submission / supplement / rebuttal / accepted
[Track + next deadline] <track and date/source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <page / anonymity / interaction evidence / supplement / presentation>
[Owner map] <task -> person or role>

More from brycewang-stanford

Other Claude Code skills by this author in the directory.

๐Ÿ“ฆ
1w ago

AAAI Artifact Evaluation

Use when preparing AAAI artifact packages โ€” code, data, appendices โ€” for peer review, ensuring anonymity, reproducibility, and compliance with AAAI's supplementary-material deadline and immutable rules.
Quality
+1%875106
โœ๏ธ
1w ago

AAAI Author Response

Draft AAAI rebuttals under tight space constraints, triaging factual errors, AI-generated reviews, and reviewer concerns while adhering to AAAI's character limit, no-URL rule, and no-new-results policy.
Writing
+1%875106
๐Ÿ“„
1w ago

AAAI Camera Ready

Prepares an accepted AAAI paper for camera-ready submission to AAAI Press, including template compliance, page limits, deanonymization, copyright transfer, and final source upload.
Writing
+1%875106
๐Ÿงช
1w ago

AAAI Experiments

A systematic audit for AAAI submissions to ensure empirical evidence supports AI contributions. Covers baselines, ablations, reproducibility, human evaluation, and alignment claims.
Quality
+1%875106
๐Ÿ“„
1w ago

AAAI Related Work

Assists authors in writing related work sections for AAAI papers that clearly differentiate novelty, handle contemporaneous non-archival work within policy constraints, and address reviewer pushback patterns.
Writing
+1%875106
๐Ÿ”
1w ago

AAAI Reproducibility

Strengthens an AAAI paper's reproducibility by auditing the checklist, evidence mapping, artifact readiness, and disclosure of seeds, compute, and data. Helps authors prepare for Phase-1 reviewer scrutiny on rigor.
Quality
+1%875106