Menu

Individual skill

jom-literature-positioning

0upvotes

Use when positioning a Journal of Operations Management (JOM) manuscript within the operations and supply chain management conversation — joining a live OM/SCM debate, distinguishing the paper from analytical OM work, and aligning the framing with the target Department's mission.

Journal-of-Operations-Management-Skills/skills/jom-literature-positioning/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Literature Positioning for JOM (jom-literature-positioning)

## When to trigger

- Your introduction lists prior studies instead of joining a debate
- A reviewer says "what conversation is this paper in?" or "how is this different from existing OM work?"
- Your citations skew toward analytical/optimization OM but your study is empirical (or vice versa)
- You are unsure which OM/SCM literature the chosen Department expects you to engage

## Join an OM/SCM conversation, don't spot a gap

A bare "no one has studied X" is weak. Position the paper as a contribution to an ongoing **operations and supply chain management** conversation: what does the field currently believe about this operational phenomenon, what tension or anomaly does your evidence expose, and how does resolving it move the OM conversation forward? Problematize a shared assumption (e.g., that more buffering always helps, that lean and resilience trade off cleanly, that automation uniformly reduces errors) rather than merely noting an empty cell.

## Distinguish from analytical OM explicitly
Back to top