jmis-theory-development
Use when building the theoretical engine of a Journal of Management Information Systems (JMIS) manuscript — an IT-business-value logic, a platform/network-effects mechanism, an economic model of IS, or a technology-specific behavioral theory. Adapts the form of "theory" to JMIS's management-and-economics-of-IS identity; it does not run the analysis (jmis-data-analysis) or frame the contribution (jmis-contribution-framing).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-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 (jmis-theory-development) ## When to trigger - Your claims are descriptive ("IT spend correlates with performance") with no economic or behavioral mechanism - You built an artifact or ran a regression but cannot say what *IS knowledge* it advances - A reviewer says "the theoretical contribution is unclear" or "this is a technical/empirical exercise" - You need hypotheses, propositions, or signed predictions derived *before* you look at results ## Theory takes a different shape in each JMIS style JMIS spans empirical, economic-analytical, and design-oriented IS work, so "develop theory" means different things. Pick the row that matches your study; JMIS's distinctive pull is toward the **economics and management of IS**, so even behavioral papers benefit from naming the value or incentive at stake. | Style | What "theory" means here | What you must produce | |-------|--------------------------|------------------------| | **IT business value** | A mechanism by which a specific IT capability creates, captures, or destroys value | Causal logic from IT capability → intermediate process → firm/market outcome, with complementarities and contingencies named | | **Platfo
- When to trigger
- Theory takes a different shape in each JMIS style
- IT business value: make the mechanism, not the correlation, the theory
- Platform and economics-of-IS: derive signed predictions a priori
- Behavioral IS: keep the artifact load-bearing
- Make boundary conditions and level of analysis explicit
- Referee pushback mapped to a theory fix
- Checklist
- Tie the theory to a managerial decision
- Anti-patterns
- Borrow reference-discipline theory, but earn an IS extension
- Output format
What does the jmis-theory-development skill do?
Use when building the theoretical engine of a Journal of Management Information Systems (JMIS) manuscript — an IT-business-value logic, a platform/network-effects mechanism, an economic model of IS, or a technology-specific behavioral theory. Adapts the form of "theory" to JMIS's management-and-economics-of-IS identity; it does not run the analysis (jmis-data-analysis) or frame the contribution (jmis-contribution-framing).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-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.