jmis-literature-positioning
Use when staking a Journal of Management Information Systems (JMIS) manuscript's contribution against the IS literature and the basket siblings — showing it advances an IS-management/economics conversation rather than only a reference discipline. Positions the work; it does not build the mechanism (jmis-theory-development) or write the contribution statement (jmis-contribution-framing).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-literature-positioning --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.
# Literature Positioning (jmis-literature-positioning) ## When to trigger - The front end reads as a reference-discipline paper (pure economics, marketing, CS, OB) that merely uses an IS setting - You cannot name the specific IS conversation you are joining and changing - A reviewer says the contribution is incremental, or that the paper "ignores prior IS work" - You are unsure whether the natural home is JMIS, MISQ, ISR, JAIS, or Management Science ## Position to an IS conversation, not just a reference discipline JMIS is an IS journal, so the literature you must engage first is the **IS literature** — IT business value, digital platforms, e-commerce, IS economics, security/privacy, decision support/analytics — even when your toolkit comes from economics or computer science. The test a JMIS reviewer applies: *what did the IS field believe, and how does this paper move that belief?* Borrowing a reference-discipline method is fine; positioning the contribution *only* in the reference discipline is a desk-reject signal because the IS audience cannot see the advance. ## Build the positioning in three moves 1. **Name the stream and its current frontier.** State the specific JMIS-releva
- When to trigger
- Position to an IS conversation, not just a reference discipline
- Build the positioning in three moves
- Engage the basket and cite the right precedents
- Use sibling boundaries to sharpen, not just to defend
- Worked vignette: turning an absence into a tension (illustrative)
- Referee pushback mapped to a repositioning move
- Checklist
- Show you know the JMIS conversation specifically
- Anti-patterns
- A three-paragraph positioning skeleton
- Keep positioning honest about what is new
- Output format
What does the jmis-literature-positioning skill do?
Use when staking a Journal of Management Information Systems (JMIS) manuscript's contribution against the IS literature and the basket siblings — showing it advances an IS-management/economics conversation rather than only a reference discipline. Positions the work; it does not build the mechanism (jmis-theory-development) or write the contribution statement (jmis-contribution-framing).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-literature-positioning --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 984 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.