jais-methods
Use when choosing and defending the research design for a Journal of the Association for Information Systems (JAIS) manuscript — a behavioral survey/experiment, an economics-of-IS identification strategy, a design-science build-and-evaluate cycle, a qualitative/interpretive study, or a review method. Matches method to the IS claim under JAIS's methodological pluralism; it designs the study and hands estimation/evaluation to jais-data-analysis.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-methods --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.
# Research Design & Methods (jais-methods) ## When to trigger - You have a theory or design propositions but no defensible way to test or evaluate them - The method may not match the claim (e.g., a causal claim resting on a cross-sectional correlation) - A reviewer asks "how do you know the artifact works?" or "what identifies this effect?" - You chose a method by habit/fashion rather than because the phenomenon demands it - You are designing a Literature Review and need a transparent, reproducible review protocol ## Pluralism is the point — but each method has its own bar JAIS is explicitly "inclusive in… method and philosophical and research approach," so there is no mandated design. That freedom comes with a duty: **justify the method by the phenomenon and the claim**, and meet the rigor norms of that method's tradition. JAIS reviewers span paradigms, so a method chosen for convenience rather than fit is a recurring rejection. Pick the row your claim requires. | Tradition | Typical designs | The design must establish | |-----------|-----------------|----------------------------| | **Behavioral** | lab/online/field experiment, multi-wave survey, panel | internal validity, constru
- When to trigger
- Pluralism is the point — but each method has its own bar
- Let the philosophical stance pick the criteria
- Behavioral: design out the threats before you collect
- Behavioral: prepare the JAIS-required measurement materials now
- Economics of IS: anchor identification in real exogenous variation
- Design science: plan the evaluation up front
- Design science: anchor in a recognized DSR tradition
- Qualitative/interpretive: make philosophical stance explicit
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Justify the method to a cross-paradigm panel
- Worked vignette: matching method to claim (illustrative)
- Anti-patterns
What does the jais-methods skill do?
Use when choosing and defending the research design for a Journal of the Association for Information Systems (JAIS) manuscript — a behavioral survey/experiment, an economics-of-IS identification strategy, a design-science build-and-evaluate cycle, a qualitative/interpretive study, or a review method. Matches method to the IS claim under JAIS's methodological pluralism; it designs the study and hands estimation/evaluation to jais-data-analysis.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jais-methods --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.