Skip to content
Content
Skill

/amj-review-process

Use when you need to understand or set expectations for the Academy of Management Journal (AMJ) editorial and peer-review process — desk review, the developmental multi-round R&R culture, and reading a decision letter. Explains the process and how to read decisions; it does not

From plugin
awesome-journal-skills
965200 skills
Install
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill amj-review-process --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/amj-review-process

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use when you need to understand or set expectations for the Academy of Management Journal (AMJ) editorial and peer-review process — desk review, the developmental multi-round R&R culture, and reading a decision letter. Explains the process and how to read decisions; it does not

SKILL.md

amj-review-process.SKILL.md
name: amj-review-process
description: Use when you need to understand or set expectations for the Academy of Management Journal (AMJ) editorial and peer-review process — desk review, the developmental multi-round R&R culture, and reading a decision letter. Explains the process and how to read decisions; it does not draft the response letter (amj-rebuttal).

Understanding the Review Process (amj-review-process)

When to trigger

  • Before submitting, to calibrate expectations about timeline and decision types
  • A decision letter arrived and you need to interpret it (R&R vs. reject; major vs. minor)
  • You are unsure how much weight reviewers vs. the action editor carry
  • You want to plan a revision strategy before drafting the response (then go to `amj-rebuttal`)

> Editorial structure, named editors, and exact timelines change. Verify the current editorial team, policies, and turnaround on the official AMJ site; the norms below are durable. As of 2026-05-30: AMJ uses **blind review**, targets constructive **developmental feedback to authors within ~60 days**, and the incoming Editor-in-Chief is **Gary A. Ballinger (University of Virginia)**, whose team began receiving submissions on 1 July 2025.

How AMJ review works (durable norms)

1. **Submission & routing.** The editor (or an associate/action editor) screens the manuscript and routes it to an action editor in the relevant division. Submission is via ScholarOne (mc.manuscriptcentral.com/AMJ) with all author identifiers removed for blind review. 2. **Desk decision.** Manuscripts that are off-fit, atheoretical, fatally underpowered, or that miss one of AMJ's three criteria (empirical contribution, theoretical contribution, practical relevance) may be desk-rejected without external review. A clear theoretical contribution and appropriate design are what get a paper past the desk. 3. **External peer review.** Typically several (often three) reviewers in the focal conversation evaluate the theoretical contribution, design rigor, and analysis; AMJ aims to return developmental feedback within roughly 60 days. 4. **Action editor synthesis.** The action editor weighs the reviews, forms an independent judgment, and writes the decision letter. The editor's letter — not a vote count — drives the outcome. 5. **Decision.** Common outcomes: reject; reject with encouragement to resubmit as new; major revision (R&R); minor revision; (rarely) accept. A first-round acceptance is essentially unheard of.

AMJ is developmental and multi-round

AMJ's culture is **developmental**: an R&R is an invitation to improve the paper over (often) multiple rounds. Reviewers and the action editor push hard on the **theoretical contribution** and the **method** — expect requests to deepen theory, add a study, strengthen identification, or address common-method/endogeneity concerns. Treat an R&R as a serious opportunity, not a near-acceptance, and not a rejection.

Reading the decision letter

  • **Find the editor's priorities first.** The action editor's letter signals which reviewer points are essential vs. optional. Address the editor's framing above all.
  • **Distinguish "fatal" from "fixable."** If a core identification or theory concern is fatal and unaddressable, an honest reframe (or a different paper) beats a doomed revision.
  • **Gauge encouragement.** Language like "we see promise" + a major revision signals a real path; "does not fit our developmental model" signals reject.
  • **Count the asks.** Map every reviewer point to: theory / method / analysis / framing / writing — this becomes the revision plan that feeds `amj-rebuttal`.

Planning the revision

  • Decide whether you can satisfy the **theoretical-contribution** demands; if not, the revision will not succeed regardless of method fixes.
  • Scope the new analyses/data the reviewers imply and whether they are feasible in the revision window.
  • Identify points where reviewers conflict; plan to surface the conflict for the editor rather than silently siding with one.

Checklist

  • [ ] Decision type identified (R&R major/minor, reject-resubmit, reject)
  • [ ] The action editor's priorities extracted and ranked above individual reviewer asks
  • [ ] Every reviewer comment categorized (theory / method / analysis / framing / writing)
  • [ ] Fatal vs. fixable concerns separated honestly
  • [ ] Feasibility of demanded new theory/data/analyses assessed against the deadline
  • [ ] Reviewer conflicts noted for the editor's attention

Anti-patterns

  • Treating an R&R as a near-acceptance and making only cosmetic changes.
  • Treating an R&R as a rejection and walking away from a viable path.
  • Counting reviewer votes instead of reading the action editor's letter.
  • Ignoring the editor's stated priorities while over-investing in a minor reviewer point.
  • Starting to write the response letter before mapping and planning the revision.

Output format

【Decision type】R&R(major/minor) / reject-resubmit / reject
【Editor's priorities】1... 2... 3...
【Comment map】theory:[...] method:[...] analysis:[...] framing:[...] writing:[...]
【Fatal vs. fixable】...
【New work needed】theory / data / analysis — feasible? ...
【Reviewer conflicts】...
【Next step】amj-rebuttal (plan revisions, then draft response)
Read more
Ships withawesome-journal-skills

Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证

Get the whole plugin
Stats
965
Stars
121
Forks
Active
Maintenance
Stata
Language
MIT
License
13h ago
Last commit
2mo ago
Created

Repo: brycewang-stanford/Awesome-Journal-Skills

Other skills on awesome-journal-skills.