pom-writing-style
Use when revising the prose of a Production and Operations Management (POM) manuscript — front-loading the operations problem, balancing theory with practice relevance, applying author-year citations, and enforcing the 32-page cap with an e-companion split. Polishes prose; it does not build the model (pom-theory-development) or design exhibits (pom-tables-figures).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-writing-style --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.
# Writing Style (pom-writing-style) ## When to trigger - The prose buries the operations problem or the managerial takeaway - The main document is over the 32-page cap - Method exposition crowds out the OM insight - Citations are not in POM's author-year style ## Write for a broad OM audience and for practicing managers POM reviewers span method specialists and broad operations scholars, and the **practice-relevance gate** means the writing must convince both. Lead with the operations problem, setting, and decision; keep the method visible but **subordinate to the OM insight**. Pair theory and practice throughout: every theoretical claim should imply an operational consequence a manager can act on. ## POM house conventions - **Citations:** author-year (name-year) parenthetical in-text (e.g., Hayes & Pisano 1996 style) with an alphabetical reference list. Configure your reference manager accordingly. - **Abstract:** maximum **350 words**, with **no formulas, references, or abbreviations**. Write it for a Department Editor: problem, method family, key result, theory contribution, practice implication. - **Title:** concise and descriptive, **≤ 25 words**; supply 1–6 keywords. - **LaTe
- When to trigger
- Write for a broad OM audience and for practicing managers
- POM house conventions
- Enforce the 32-page discipline
- Revision targets
- Before/after micro-rewrites in POM's register
- Checklist
- Style execution pass for Production and Operations Management
- Output format
What does the pom-writing-style skill do?
Use when revising the prose of a Production and Operations Management (POM) manuscript — front-loading the operations problem, balancing theory with practice relevance, applying author-year citations, and enforcing the 32-page cap with an e-companion split. Polishes prose; it does not build the model (pom-theory-development) or design exhibits (pom-tables-figures).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-writing-style --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.