agentsclimarketplace

Pom literature positioning

Skill brycewang-stanford/Awesome-Journal-Skills/Production-and-Operations-Management-Skills/skills/pom-literature-positioning

Use when positioning a Production and Operations Management (POM) manuscript within an operations conversation — against the target Department's prior work and adjacent OM journals (M&SOM, Management Science, Operations Research, JOM). Positions the paper; it does not build the model (pom-theory-development) or state the contribution (pom-contribution-framing).From its SKILL.md

Install
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-literature-positioning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

4.6 KB, 878 tokens by cl100k_base, as published. Nobody here has run it

Literature Positioning (pom-literature-positioning)

When to trigger

  • The front end reads as gap-spotting ("no one has modeled X")
  • Reviewers from the target Department will know a literature you have not engaged
  • You must distinguish a same-data or closely related paper from prior work
  • You are unsure whether POM (vs. a narrower venue) is the right home

Position within the right Department's conversation

Because POM routes to a named Department, positioning is department-specific: a Behavioral Operations paper joins a different conversation than a Supply Chain Management or Healthcare Operations paper, even with similar methods. Anchor first in the relevant OM stream, then in the method or application literature. Engage the canonical work that the Department Editor and reviewers will expect.

Map the adjacent OM landscape

Compare deliberately against POM and its neighbors, and say why POM is the home:

  • M&SOM, Management Science (Operations), Operations Research — often more model-leaning or method-deep.
  • Journal of Operations Management, IJOPM, Decision Sciences — frequently more empirical/process-oriented.
  • Domain outlets (healthcare, transportation, sustainability) for the application.

State why POM fits: the paper combines rigor with significant interest to practicing operations managers — POM's distinctive gate.

Separate the axes of novelty

Be explicit about which novelty you claim, so reviewers do not collapse them:

  • Setting (new operational context) · mechanism (new operations logic) · model/method (new formulation or estimator) · data (new operations data) · managerial implication (new decision lever).

A new setting alone rarely clears the POM bar; a new mechanism or decision lever usually does.

Handle same-data / related work transparently

POM requires the cover letter to outline all closely related prior works using the same data, subsets, or project. In the manuscript, cite that prior work and state precisely what is new here — silent overlap is an integrity problem, not just a positioning weakness.

Positioning paragraph pattern

Prior OM work [in Department X] explains <known mechanism>.
It has not shown <missing mechanism / setting / evidence>.
This paper contributes <new insight>, using <method/evidence>.
POM is the home because <rigor + practicing-manager relevance + department fit>.

Checklist

  • Anchored in the target Department's canonical stream
  • Adjacent OM journals contrasted; POM-as-home justified
  • Novelty axis (setting/mechanism/method/data/implication) named, not blurred
  • Same-data/related work cited and distinguished
  • Must-add citations identified

Positioning pass for Production and Operations Management

Treat this skill as an executable review pass, not a prose hint. First lock the operational decision, the performance metric, and the implementable lever; then judge whether the current manuscript answers the venue's real reader: POM reviewers who want operational insight tied to production, service, supply-chain, or platform decisions.

  • Do the pass: Build a three-column map: incumbent conversation, unresolved tension, and this manuscript's delta; include one sibling-venue omission that would make a referee doubt the fit.
  • Return a ledger: give claim / evidence / risk / manuscript location rows, so the next agent can edit rather than rediscover the issue.
  • Sibling guard: compare against Management Science for broader OR/MS theory, Operations Research for method-first optimization, MSOM for manufacturing/service operations depth; if a sibling owns the contribution, recommend re-routing before polishing format.
  • Stop condition: do not give submission-ready advice until the pack's resources/official-source-map.md has been checked for volatile rules and the manuscript has one concrete fix for the largest venue-specific risk.

Output format

【Department conversation】stream + canonical work
【Closest paper】citation or placeholder
【Novelty axis】setting / mechanism / method / data / implication
【Same-data disclosure】related prior work distinguished? yes/no
【Positioning paragraph】<text>
【Next step】pom-methods or pom-contribution-framing

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.