Menu

Individual skill

misq-literature-positioning

0upvotes

Use when positioning a MIS Quarterly manuscript inside the right information-systems conversation — engaging canonical IS work, showing the IT artifact is central, and distinguishing the paper from adjacent IS venues (ISR, JMIS, JAIS) and from the parent reference disciplines (management, economics, computer science).

MIS-Quarterly-Skills/skills/misq-literature-positioning/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Literature Positioning (misq-literature-positioning)

## When to trigger

- Your front end reads as "no one has studied X" (gap-spotting) rather than joining a conversation
- A reviewer says "this belongs in [a reference discipline] journal" or "the IS contribution is unclear"
- You cite mostly non-IS work and little of the canonical IS literature
- You cannot articulate what an IS scholar — versus a management, economics, or CS scholar — gains

## Join an IS conversation, do not just find a gap

MISQ rewards problematization over gap-spotting: surface and challenge an assumption in the existing IS literature, then show why resolving it matters. State explicitly *which* IS conversation you join (e.g., technology adoption and use, IT value and productivity, digital platforms and markets, IS security and privacy, IS development and design, the future of work). Cite the canonical anchors of that conversation, not just recent adjacent papers.

## Keep the IT artifact central
Back to top