Organization Studies Skills
Agent skill stack for manuscripts targeted at Organization Studies (OS). Twelve role skills cover fit, contribution, evidence, writing, submission, and revision with source-backed OS guardrails.
Skills in this plugin
12- ▌ Orgstud Methods · brycewang-stanfordUse 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).
- ▌ Orgstud Rebuttal · brycewang-stanfordUse when drafting the response to reviewers and the revision plan for an Organization Studies (OS) R&R — turning developmental, theory-level reviewer comments into a credible point-by-point reply and revised manuscript. Plans and drafts the response; it does not redo the underlying analysis (route back to the specialist skills).
- ▌ Orgstud Workflow · brycewang-stanfordUse when deciding which orgstud-* sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for an Organization Studies (OS) submission. Routes — it does not replace — the specialized skills.
- ▌ Orgstud Submission · brycewang-stanford bundleUse when running the final pre-submission preflight for Organization Studies (OS) via ScholarOne — double-anonymization, the 13,000-word cap, the 300-word unstructured abstract, the keyword rule, and SAGE house format. Final checks; it does not draft content.
- ▌ Orgstud Data Analysis · brycewang-stanfordUse when executing and reporting the analysis for an Organization Studies (OS) manuscript — qualitative coding and the data-to-theory ladder, process analysis, or quantitative estimation and robustness. Makes the evidence-to-theory link transparent; it does not design the study (see orgstud-methods).
- ▌ Orgstud Writing Style · brycewang-stanfordUse for full-manuscript prose and the discursive European register of an Organization Studies (OS) manuscript — voice, theoretical texture, the argument's arc, and qualitative craft. Polishes the writing; it does not change the theory or analysis.
- ▌ Orgstud Review Process · brycewang-stanfordUse when calibrating expectations for the Organization Studies (OS) review cycle — desk-screen odds, the developmental double-anonymized process, decision types, and how to read what reviewers and the handling editor are signalling. Sets expectations and reading strategy; it does not draft the response (see orgstud-rebuttal).
- ▌ Orgstud Tables Figures · brycewang-stanfordUse when building the exhibits for an Organization Studies (OS) manuscript — data structures, process-model figures, evidence tables, and (for quantitative work) results tables. Designs exhibits that make the inference auditable; it does not run the analysis (see orgstud-data-analysis).
- ▌ Orgstud Topic Selection · brycewang-stanfordUse when choosing or sharpening the phenomenon and research question for an Organization Studies (OS) manuscript — testing whether it is theoretically generative for OS's European organization-theory audience. Diagnoses fit and scope; it does not build the theory or run analysis.
- ▌ Orgstud Theory Development · brycewang-stanfordUse when building the theoretical engine for an Organization Studies (OS) manuscript — the mechanism, process model, or conceptual move that constitutes the contribution. Builds the argument; it does not select methods or run analysis.
- ▌ Orgstud Contribution Framing · brycewang-stanfordUse when sharpening the one-sentence theoretical contribution of an Organization Studies (OS) manuscript and the intro/discussion claims that carry it. Frames the contribution; it does not build the theory (see orgstud-theory-development) or run analysis.
- ▌ Orgstud Literature Positioning · brycewang-stanfordUse when staking the contribution of an Organization Studies (OS) manuscript against the specific theoretical conversation it joins — what the field knows, what it misses, and the precise gap this paper closes. Positions the argument; it does not build the theory (see orgstud-theory-development) or run analysis.