orgstud-methods
Use when choosing and justifying the research design for an Organization Studies (OS) manuscript — qualitative/ethnographic, process, historical, or quantitative — and setting the rigor bar OS reviewers expect. Designs the study; it does not run the analysis (see orgstud-data-analysis).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-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.
# Methods & Research Design (orgstud-methods) ## When to trigger - You are choosing between a qualitative/process design and a quantitative one - The design is chosen but its *rigor and transparency* are not yet defensible to OS reviewers - A qualitative study lacks a sampling logic, immersion account, or trustworthiness safeguards - A quantitative study leads with the estimator instead of the organizational mechanism it reveals ## Method follows the theoretical question — and OS leans qualitative At OS, **no method is privileged in principle**, but the journal's center of gravity is **qualitative, ethnographic, process, and historical** research, and such work is genuinely first-class here — not a tolerated minority. The non-negotiable is that the design fits the question (see `orgstud-theory-development`) and is executed with craft. A sophisticated estimator cannot rescue a thin theory, and a single immersive case can carry an OS paper if the theoretical insight is deep — a different bar from venues where a clean identification design is itself treated as the contribution. OS reviewers ask, above all, *does this design let you see the organizing process you claim to theorize?* ##
- When to trigger
- Method follows the theoretical question — and OS leans qualitative
- Branch A — Qualitative / process / ethnographic / historical
- Branch B — Quantitative organization theory
- Either branch
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Output format
What does the orgstud-methods skill do?
Use when choosing and justifying the research design for an Organization Studies (OS) manuscript — qualitative/ethnographic, process, historical, or quantitative — and setting the rigor bar OS reviewers expect. Designs the study; it does not run the analysis (see orgstud-data-analysis).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-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.