Individual skill
jom-theory-development
Use when building the theoretical argument and hypotheses for a Journal of Operations Management (JOM) empirical study — deriving operations/behavioral mechanisms a priori, borrowing and adapting reference theory to an OM phenomenon, and specifying mediation/moderation so they are testable against observed operations data.
Journal-of-Operations-Management-Skills/skills/jom-theory-development/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- 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,411
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,182 bytes
Read excerpt
# Theory Development for Empirical OM (jom-theory-development)
## When to trigger
- Your hypotheses describe what happens but not *why*, operationally
- You are importing a reference theory (TCE, RBV, agency, institutional, behavioral decision theory, contingency, queueing/coordination logic) and must adapt it to an operations setting
- A reviewer says "this is a correlation, not a mechanism" or "the theory could apply to any context"
- You need to specify mediators/moderators that operations data can actually identify
## JOM's theory bar
JOM is empirical, but empirical strength without theory reads as a technical report. The argument must give an **operations mechanism** — a causal logic rooted in how work, capacity, inventory, information, incentives, or human behavior in operations actually function — not a generic management story bolted onto an OM dataset. Because JOM explicitly excludes purely analytical/optimization work, your theory is *verbal and falsifiable*, developed to be tested against **observation**, not derived as an optimization proof.
## Build the mechanism a priori