本文へ移動
cccskills
無料GitHub で公開

amj-rebuttal

Use when drafting the revision and response letter after an Academy of Management Journal (AMJ) revise-and-resubmit — structuring point-by-point responses to the action editor and reviewers across a multi-round developmental process. Drafts the response after revisions; it does not interpret the decision letter (amj-review-process).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

R&R Response & Rebuttal (amj-rebuttal)

When to trigger

  • You received an AMJ R&R and have planned the revision (via amj-review-process)
  • You have actually made (or scoped) the manuscript changes and need to write the response document
  • You must reconcile conflicting reviewer demands for the action editor
  • A later-round decision asks you to defend or further revise prior changes

Write the response letter after revising the manuscript, not before. The letter documents changes you have made, not promises. AMJ's process is developmental and typically multi-round; resubmit the revised manuscript and response document through ScholarOne (mc.manuscriptcentral.com/AMJ), keeping the same action editor across rounds where possible, and remember the revised main body still must respect the 40-page limit (text + references + appendices).

Response-document structure

  1. Opening letter to the action editor. Thank the editor and reviewers; summarize the most important changes in 2–4 sentences; explicitly state how you addressed the editor's stated priorities. Note where reviewers conflicted and how you resolved it.
  2. Per-reviewer sections. For each reviewer, restate every comment verbatim (or faithfully numbered), then respond.
  3. Point-by-point format for each comment:
    • Comment (quoted/numbered)
    • Response (what you did and the theoretical/methodological reasoning)
    • Location (section/page/table where the change appears)
    • Quote the new manuscript text where helpful.

How to respond to AMJ's signature demands

  • "Deepen the theoretical contribution." Strengthen the mechanism and the contribution sentences; show what the field now learns. Do not just add citations — revise the argument (see amj-theory-development, amj-contribution-framing).
  • "Strengthen the method / address endogeneity." Add the identification strategy, robustness, or a supplementary study; report it and explain why it resolves the concern (see amj-methods, amj-data-analysis).
  • "Common-method bias." Provide designed or additional evidence; if you cannot collect new data, give the strongest available statistical evidence and acknowledge residual risk as a boundary.
  • "Add a study." If feasible, an experiment or replication that nails the mechanism is often the decisive move in the developmental process — but watch the 40-page budget: heavy new material often lives in an online supplement so the main body stays within limit.

Tone and tactics

  • Be respectful and substantive. Reviewers are colleagues investing in your paper; thank them and engage seriously, even when disagreeing.
  • Concede gracefully where they are right; make the change.
  • Disagree with evidence, not assertion. If you decline a request, give a theoretical or empirical reason and, where possible, an alternative analysis showing robustness.
  • Address every point. Silent omissions read as evasion; a non-trivial point left unanswered can sink a revision.
  • Surface conflicts to the editor. When reviewers ask for opposite things, explain the trade-off and your chosen resolution for the editor to adjudicate.
  • Keep it self-contained. A reviewer should not have to hunt the manuscript to see what changed.

Checklist

  • Manuscript actually revised before the letter was written
  • Editor's priorities addressed first and explicitly in the opening letter
  • Every reviewer comment restated and answered (none skipped)
  • Each response names the location of the change and quotes new text where useful
  • Theory-contribution and method/endogeneity demands met with real changes, not citations only
  • Declined requests are justified with evidence and, where possible, an alternative test
  • Reviewer conflicts surfaced and resolved for the editor
  • Tone is collegial and confident throughout

Anti-patterns

  • Writing the response before making the changes.
  • Skipping or burying an inconvenient comment.
  • Responding "we have added a citation" to a "deepen the theory" request.
  • Defensive or dismissive tone toward reviewers.
  • Declining a request with assertion ("we believe this is fine") and no evidence.
  • Silently siding with one reviewer when two conflict, leaving the editor to discover it.

Output format

【Decision round】1st R&R / 2nd round / ...
【Editor priorities addressed】1... 2... 3...
【Per-reviewer coverage】R1: x/x comments, R2: x/x, R3: x/x — all answered? yes/no
【Major changes】theory: ... method/data: ... new study: ...
【Declined requests + justification】[...]
【Reviewer conflicts resolved】...
【Response letter status】drafted / final
【Next step】resubmit via ScholarOne; on next decision → amj-review-process

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

brycewang-stanford のスキルをすべて見る

このスキルの問題を報告する