jmgmt-theory-development
Use when the theoretical argument is the bottleneck for a Journal of Management (JOM) manuscript — building constructs, mechanisms, boundary conditions, and a priori hypotheses (or a review's organizing framework). Constructs the theory; it does not run the analysis (jmgmt-data-analysis) or write the contribution paragraph (jmgmt-contribution-framing).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmgmt-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 (jmgmt-theory-development) ## When to trigger - Hypotheses read as bald predictions ("A is positively related to B") with no mechanism - You have results and are tempted to write hypotheses around them (HARKing risk) - The argument leans on one borrowed theory name (e.g., "social exchange") without using its logic - Mediators/moderators sit in the data but are not theorized - A meta-analysis or review needs an **organizing framework**, not just a coding scheme - A reviewer says "the theory is thin," "underdeveloped," or "why would this be true?" ## The JOM theory bar JOM publishes empirical, theoretical, *and* review work, but in every case the **theoretical contribution is the gate**. For an empirical paper, each hypothesis must be **derived from an articulated mechanism, before the results are known**, and a reader should finish the front end understanding *why* the effect occurs and *under what conditions* it strengthens or reverses. For a **meta-analysis**, the synthesis must be organized by theory so that moderators *adjudicate* competing accounts — JOM does not reward a coefficient census. For a **systematic review** (Review Issue), the deliverable is an
- When to trigger
- The JOM theory bar
- Building a hypothesis (the mechanism chain)
- Constructs earn their keep
- Mediation, moderation, and rival theories
- Theory for a review or meta-analysis
- Worked vignette (illustrative)
- Checklist
- Anti-patterns
- Output format
What does the jmgmt-theory-development skill do?
Use when the theoretical argument is the bottleneck for a Journal of Management (JOM) manuscript — building constructs, mechanisms, boundary conditions, and a priori hypotheses (or a review's organizing framework). Constructs the theory; it does not run the analysis (jmgmt-data-analysis) or write the contribution paragraph (jmgmt-contribution-framing).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmgmt-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.