jms-theory-development
Use when the theoretical argument is the bottleneck for a Journal of Management Studies (JMS) manuscript — building a mechanism and deriving hypotheses a priori, OR abstracting grounded constructs and propositions from qualitative data. Constructs the theory both deductively and inductively; it does not run the analysis (jms-data-analysis) or write the final contribution paragraph (jms-contribution-framing).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-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 (jms-theory-development) ## When to trigger - Hypotheses read as bald predictions ("A is positively related to B") with no mechanism - An inductive study produces rich description but no abstracted theoretical model - The argument leans on one borrowed citation rather than a developed logic - A reviewer says "the theory is thin," "this is description, not theory," or "what is the contribution to theory?" - You are unsure whether to write a priori hypotheses or emergent propositions ## The JMS theory bar 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. ## Path A — Deductive: build a hypothesis as a mechanism chain For each hypothesis, write the explicit chain and skip no step: 1. **Antecedent** — the predictor and why it matters in this
- When to trigger
- The JMS theory bar
- Path A — Deductive: build a hypothesis as a mechanism chain
- Path B — Inductive: abstract data into a grounded theoretical model
- Engage rival explanations
- Checklist
- Anti-patterns
- Output format
What does the jms-theory-development skill do?
Use when the theoretical argument is the bottleneck for a Journal of Management Studies (JMS) manuscript — building a mechanism and deriving hypotheses a priori, OR abstracting grounded constructs and propositions from qualitative data. Constructs the theory both deductively and inductively; it does not run the analysis (jms-data-analysis) or write the final contribution paragraph (jms-contribution-framing).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-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.