Individual skill

msom-writing-style

Use when polishing the prose of a Manufacturing & Service Operations Management (M&SOM) manuscript — front-loading the operational insight, controlling mathematical notation, writing the structured abstract, and applying INFORMS author-year house style within the 32-page typeset cap. Late-stage polish; do not invoke before the model/identification is settled.

Manufacturing-and-Service-Operations-Management-Skills/skills/msom-writing-style/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

# Writing Style (msom-writing-style)

## When to trigger

- The introduction buries the operational insight under notation or literature
- The structured abstract is missing a required part or is jargon-heavy
- Notation is dense, inconsistent, or front-loaded before motivation
- You are reconciling the manuscript to INFORMS author-year style and the page cap

## Lead with the operations insight, not the math

M&SOM readers are operations researchers, but the journal prizes **clarity** and **managerial relevance** alongside technical validity. Open by stating the **operational problem, the decision, and the insight** in words before equations. Introduce notation only when it is needed; a reader should grasp the contribution from the introduction without parsing a model. For analytical papers, narrate the *structure* of the result ("the optimal policy is a threshold that…") rather than dumping the theorem first.

## Write the mandatory structured abstract
Back to top