pom-review-process
Use when understanding or planning for Production and Operations Management (POM) review — Department Editor screening, double-blind review, the rigor-and-practice evaluation, and the strict no-resubmission-after-rejection rule. Explains the process and reads decisions; it does not draft the response (pom-rebuttal).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-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.
# Review Process (pom-review-process) ## When to trigger - You want to understand how POM evaluates papers before or after submitting - You received a decision letter and need to read it correctly - You are tempted to resubmit a rejected paper and need to know the rule ## How POM review works POM routes each submission to a **Department**, where a **Department Editor** owns the paper end to end — this department/college structure is a defining POMS norm, distinct from a single central editor. The Department Editor screens for fit and contribution, then manages **double-blind** peer review. Founder & Editor-in-Chief **Kalyan Singhal** (University of Baltimore) leads the journal, with **Subodha Kumar** as Co-Editor-in-Chief (verified via POMS / SAGE, 2026-06-22; re-check the masthead before relying on it). ## What reviewers weigh POM applies a **twin standard**: scholarly rigor **and** significant interest to practicing operations managers. Expect two lenses: - **Method specialists** scrutinize assumptions, proofs, identification, validation, and robustness within your track (analytical/empirical/behavioral/data-science). - **Broad OM reviewers** ask whether the insight generalizes a
- When to trigger
- How POM review works
- What reviewers weigh
- The strict no-resubmission rule
- Reading the decision letter
- Checklist
- Review-risk pass for Production and Operations Management
- Output format
What does the pom-review-process skill do?
Use when understanding or planning for Production and Operations Management (POM) review — Department Editor screening, double-blind review, the rigor-and-practice evaluation, and the strict no-resubmission-after-rejection rule. Explains the process and reads decisions; it does not draft the response (pom-rebuttal).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-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.