jais-literature-positioning
Use when positioning a Journal of the Association for Information Systems (JAIS) manuscript against the IS conversation — engaging the right cross-disciplinary literatures, citing the IS canon and JAIS's own discourse, and staking the gap the theory will fill. Builds the front-end argument; it does not build the theory itself (jais-theory-development) or run the review's method (jais-methods, for Literature Review submissions).
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-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 (jais-literature-positioning) ## When to trigger - Your introduction reads as "no one has studied X" gap-spotting rather than joining a live debate - You borrow heavily from a reference discipline but never connect to the IS conversation - A reviewer says the paper "does not engage the relevant IS literature" or "reinvents a known result" - You are unsure which IS sub-tradition's scholars are your reviewers, and so which canon to cite - You cannot answer "why JAIS rather than ISR / MISQ / JMIS" from the front end alone - You are writing a Literature Review submission and need to justify *which* literature and *why* ## What positioning is for at JAIS Positioning is not a courtesy survey of prior work; at a theory-forward journal it is where you earn the right to make a contribution. The front end must convince a pluralistic editor of three things in quick succession: that there is a live IS conversation worth advancing, that you know it well enough to move it, and that JAIS is where this move belongs. Everything else in the paper — theory, method, evidence — is read against the stake you set here. Weak positioning is not a stylistic flaw; it is the most comm
- When to trigger
- What positioning is for at JAIS
- Position for a pluralistic, theory-forward audience
- Build the positioning in three moves
- Position relative to the siblings, explicitly
- Two failure modes JAIS reviewers name by name
- Cite JAIS's own discourse where it exists
- For Literature Review submissions, positioning is the method
- Checklist
- Referee pushback mapped to the positioning fix
- Worked vignette (illustrative)
- Anti-patterns
- Output format
What does the jais-literature-positioning skill do?
Use when positioning a Journal of the Association for Information Systems (JAIS) manuscript against the IS conversation — engaging the right cross-disciplinary literatures, citing the IS canon and JAIS's own discourse, and staking the gap the theory will fill. Builds the front-end argument; it does not build the theory itself (jais-theory-development) or run the review's method (jais-methods, for Literature Review submissions).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-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 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.