Agent skill · Data & Analytics

pom-theory-development

Use when building the model or mechanism for a Production and Operations Management (POM) manuscript — formalizing assumptions, deriving equilibria/propositions for analytical work, or developing OM hypotheses for empirical/behavioral work. Builds the argument; it does not run the analysis (pom-data-analysis) or frame the contribution (pom-contribution-framing).

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-theory-development --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Production-and-Operations-Management-Skills/skills/pom-theory-development/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Model & Theory Development (pom-theory-development) ## When to trigger - You have an operations question but no formal model or sharp mechanism - Your assumptions are mathematically convenient but operationally unmotivated - A reviewer says "the model is not well grounded in practice" or "the mechanism is unclear" - Empirical results are interpreted as bare correlations with no operations mechanism ## POM's dominant track: analytical modeling — done rigorously POM is historically anchored in **analytical/mathematical modeling** (operations-research / management-science-style optimization, stochastic modeling, and game theory), so theory development most often means **building a model**, not deriving verbal hypotheses. Make every modeling choice defensible: - **Decision primitive & objective.** Name the operational decision (capacity, inventory, pricing, scheduling, sourcing, routing, staffing) and the objective (cost, profit, fill rate, waiting time, welfare). - **Assumptions tied to operations reality.** Justify each assumption (lead times, demand distribution, information structure, rationality) against an operational constraint — not analytical convenience. - **Solution concep

What's inside
Steps it walks through
  1. When to trigger
  2. POM's dominant track: analytical modeling — done rigorously
  3. Empirical, behavioral, and data-science tracks
  4. The practice-relevance gate
  5. Checklist
  6. Anti-patterns
  7. Operating pass for Production and Operations Management
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the pom-theory-development skill do?

Use when building the model or mechanism for a Production and Operations Management (POM) manuscript — formalizing assumptions, deriving equilibria/propositions for analytical work, or developing OM hypotheses for empirical/behavioral work. Builds the argument; it does not run the analysis (pom-data-analysis) or frame the contribution (pom-contribution-framing).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-theory-development --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.

Keep going