From pom-skills
Positions a POM manuscript within operations literature by anchoring in the target Department's prior work and contrasting with adjacent OM journals.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pom-skills:pom-literature-positioningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- The front end reads as gap-spotting ("no one has modeled X")
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.
Compare deliberately against POM and its neighbors, and say why POM is the home:
State why POM fits: the paper combines rigor with significant interest to practicing operations managers — POM's distinctive gate.
Be explicit about which novelty you claim, so reviewers do not collapse them:
A new setting alone rarely clears the POM bar; a new mechanism or decision lever usually does.
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.
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>.
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.
claim / evidence / risk / manuscript location rows, so the next agent can edit rather than rediscover the issue.resources/official-source-map.md has been checked for volatile rules and the manuscript has one concrete fix for the largest venue-specific risk.【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
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin pom-skillsPositions a Manufacturing & Service Operations Management (M&SOM) manuscript within established OM streams, selects the target editorial Department, and frames the contribution as joining an operational conversation.
Positions a JOM manuscript within OM/SCM debates by joining a live conversation, distinguishing empirical from analytical work, and aligning framing with the target Department's mission.
Routes between pom-* sub-skills for Production and Operations Management (POM) manuscript workflow, from topic selection through rebuttal. Identifies method track and next skill based on current manuscript stage.