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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-theory-development --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 1. **Name the operations phenomenon and its level** (task, shift, line, plant, project, dyad, supp
- When to trigger
- JOM's theory bar
- Build the mechanism a priori
- Behavioral vs. operational vs. organizational logic
- Mediation / moderation
- Anti-patterns
- Matching the mechanism engine to the evidence
- Desk-reject and return triggers on theory
- Worked vignette: building an operations mechanism a priori
- Theory objections and the mechanism-grounded fix
- Output format
What does the jom-theory-development skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-theory-development --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.