Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when the theoretical argument is the bottleneck for a Journal of Management (JOM) manuscript — building constructs, mechanisms, boundary conditions, and a priori hypotheses (or a review's organizing framework). Constructs the theory; it does not run the analysis (jmgmt-data-analysis) or write the contribution paragraph (jmgmt-contribution-framing).
Use when the prose, introduction, or abstract is the bottleneck for a Journal of Management (JOM) manuscript — the theory-forward intro, the 250-word abstract, the 15-word title, APA voice, and enforcing the 50-page (inclusive) limit. Polishes the writing; it does not build the contribution (jmgmt-contribution-framing) or fix exhibits (jmgmt-tables-figures).
Use when turning results into an explicit contribution for a Journal of Management Information Systems (JMIS) manuscript — an advance to an IS-management/economics conversation with theoretical and managerial implications. Frames the contribution and aligns intro/discussion; it does not position the literature (jmis-literature-positioning) or run the submission preflight (jmis-submission).
Use when staking a Journal of Management Information Systems (JMIS) manuscript's contribution against the IS literature and the basket siblings — showing it advances an IS-management/economics conversation rather than only a reference discipline. Positions the work; it does not build the mechanism (jmis-theory-development) or write the contribution statement (jmis-contribution-framing).
Use when planning and drafting the response to a Journal of Management Information Systems (JMIS) major/minor revision — a point-by-point reply to the EIC, Associate Editor, and double-anonymized referees that resolves identification, measurement, contribution, and robustness concerns. Plans and drafts the response; revisit earlier jmis-* skills to execute the underlying fixes.
Use when building the theoretical engine of a Journal of Management Information Systems (JMIS) manuscript — an IT-business-value logic, a platform/network-effects mechanism, an economic model of IS, or a technology-specific behavioral theory. Adapts the form of "theory" to JMIS's management-and-economics-of-IS identity; it does not run the analysis (jmis-data-analysis) or frame the contribution (jmis-contribution-framing).
Use when deciding whether a question is the right shape for a Journal of Management Information Systems (JMIS) manuscript — an IS-management or economics-of-IS problem, not a generic tech study or a pure CS contribution. Pressure-tests fit and outlet choice before theory work begins; it does not build the mechanism (jmis-theory-development).
Use when the prose is the bottleneck for a Journal of Management Information Systems (JMIS) manuscript — an abstract and introduction that land the IS-management contribution, and a body that reads for a method-literate but management-minded IS audience. Late-stage polish; do not invoke before the mechanism, identification, and contribution are settled.
Use when a Journal of Marketing Research (JMR) Revise-and-Resubmit arrives — planning the revision and drafting a point-by-point response that satisfies two independent reviewers and the Coeditor, addresses rigor-bar concerns (identification, exact statistics, replication) and substance-bar concerns (contribution), and uses the 'W'-prefixed Web Appendix to absorb new analyses without breaking the 50-page limit.
Use when the "so what for management theory and practice" is the bottleneck for a Journal of Management Studies (JMS) manuscript — sharpening the one-sentence contribution and the implications. Crystallises the claim; it does not build the theory (jms-theory-development) or position against the literature (jms-literature-positioning).