jom-review-process
Use when understanding how Journal of Operations Management (JOM) evaluates submissions — the Department-routed structure, the asymmetric double-anonymous review, the Empirical Research Methods method check, and how to read a JOM decision letter before or after submitting.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-review-process --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Understanding JOM Review (jom-review-process) ## When to trigger - You want to know what happens to a manuscript after submission - You received a JOM decision letter and need to interpret it - You are unsure who sees your identity and who evaluates the operations contribution - You want to anticipate the method check before submitting ## The Department-routed pipeline JOM is organized into **12 Departments**, each with its own Department Editors and mission. Your submission is routed to a Department (you named two, one preferred). The Department Editor oversees evaluation within that Department's conversation, typically assigning an Associate Editor who manages reviewers from the Editorial Review Board (ERB) and elsewhere. This is analogous to, but distinct from, INFORMS-style departmental area-editor routing. ## Asymmetric double-anonymous review Review is double-anonymous, with a specific asymmetry: **author identities are shared with the Editors-in-Chief and Department Editors but not with reviewers or Associate Editors** (and author-blind to those parties; vice versa). Keep the manuscript fully anonymized — reviewers and AEs must not be able to infer you. ## The Empirical Re
- When to trigger
- The Department-routed pipeline
- Asymmetric double-anonymous review
- The Empirical Research Methods method check
- Likely decisions
- Reading the letter
- Who sees what, and who decides
- What desk-rejects before review
- Worked vignette: reading a major-revision letter
- Referee and editor signals to decode
- Output format
What does the jom-review-process skill do?
Use when understanding how Journal of Operations Management (JOM) evaluates submissions — the Department-routed structure, the asymmetric double-anonymous review, the Empirical Research Methods method check, and how to read a JOM decision letter before or after submitting.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-review-process --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.