From jms-skills
Builds deductive mechanism chains or inductive grounded models for Journal of Management Studies manuscripts. Use when theory is the bottleneck.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jms-skills:jms-theory-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Hypotheses read as bald predictions ("A is positively related to B") with no mechanism
JMS exists to advance management and organization theory, and — unlike a US empirical journal — it treats the deductive and inductive paths as equally legitimate. The bar is the same for both: a reader must finish understanding why the relationship or pattern holds and under what conditions it changes. Pick the path the design demands; do not force a qualitative study into a hypothetico-deductive template or write post-hoc hypotheses around quantitative results.
For each hypothesis, write the explicit chain and skip no step:
Keep hypotheses to a defensible set (a focal effect plus a mechanism and one or two boundaries); a "kitchen sink" of ten thin predictions signals weak theory. A boxes-and-arrows model figure must map one-to-one to the hypotheses.
For qualitative theory-building, JMS does not want a priori hypotheses — it wants a credible journey from data to a model. The Gioia-style discipline is the field reference:
Make the data-to-theory chain visible (a data-structure figure plus representative quotes table is the convention) so a reviewer can audit how a quote became a construct. For process/longitudinal work, use temporal bracketing or a visual-mapping strategy and theorise the mechanism of change over time, not just a stage sequence.
Whichever path you take, name at least one alternative theoretical account and show why yours explains the phenomenon better or differently. JMS reviewers reward a paper that takes the strongest counter-theory seriously, not one that ignores it.
【Path】deductive (hypotheses) / inductive (grounded model)
【Focal theory / conversation】... (process verb: ...)
【Deductive】H1 antecedent→mechanism→outcome (level); H2 mechanism; H3+ boundary+reason
【Inductive】first-order → second-order → aggregate dimensions → propositions
【Model figure】matches hypotheses/propositions one-to-one? yes/no
【Rival explanation engaged】...
【Next step】jms-literature-positioning, then jms-methods
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jms-skillsBuilds theoretical arguments for Journal of Management manuscripts: constructs, mechanisms, boundary conditions, and a priori hypotheses. Use when theory is the bottleneck.
Builds theoretical mechanisms and derives testable hypotheses for AMJ manuscripts. Use when hypotheses lack a mechanism or a reviewer flags thin theory.
Articulates organizational mechanisms, bridges micro-macro levels, and guides choice between deductive and inductive theory building for Organization Science manuscripts.