Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Pom Review Process

ASecurity

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).

1,052 stars
0 votes
0 copies
0 views
Added 6/6/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pom Review Process?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Pom Review Process
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-pom-review-process/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-pom-review-process)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: pom-review-process
description: 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).
---

# 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 leads the journal, with Subodha Kumar as Co-/Deputy Editor-in-Chief (title varies by source; 待核实).

## 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 and **changes an operations decision**. A technically clean paper with thin managerial relevance can still be rejected.

The practice-relevance gate is real and is reinforced by POMS's award culture (e.g., Wickham Skinner, Martin K. Starr, the J. George Shanthikumar Best Data Science and eOperations Paper, and the Cheryl Gaimon Best Innovation Paper), which honor papers tied to specific departments at the POMS Annual Conference.

## The strict no-resubmission rule

POM is **stricter than most peers**: a paper **rejected** in one department may **not** be resubmitted to the same *or a different* department of the journal **unless the decision letter explicitly invited resubmission**. Read the letter carefully — only an explicit invitation reopens the door. An R&R ("revise and resubmit") *is* such an invitation; a reject is not, and reframing a reject as a new submission risks a desk reject and reputational cost.

## Reading the decision letter

- **R&R / major or minor revision:** route to `pom-rebuttal`; keep the same Department Editor across rounds. Revised manuscripts still respect the **32-page** main-document cap.
- **Reject:** unless resubmission is explicitly invited, the paper cannot return to POM — target another OM venue (M&SOM, Management Science, JOM, IJOPM, a domain journal).

## Checklist

- [ ] Department route and editor identified
- [ ] Both rigor and practice-relevance concerns separated in the letter
- [ ] Decision type classified (R&R vs. reject) correctly
- [ ] Resubmission invitation present? (only path back after a reject)
- [ ] Revised page budget plan if proceeding

## Output format

```
【Decision type】R&R (major/minor) / reject / reject-with-invitation
【Department】<department + editor>
【Concern axes】fit / contribution / method / practice relevance / presentation
【Resubmission allowed?】yes (invited) / no
【Best action】revise via pom-rebuttal / move to another OM venue
【Next step】pom-rebuttal (if R&R)
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →