ors-workflow
Use as the router for an Operations Research (OR) manuscript — given where you are in the OR/MS modeling-to-submission lifecycle, it names the next ors-* skill to invoke. Routes; it does not itself formulate models (ors-theory-development), prove results (ors-methods), or run computational studies (ors-data-analysis).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-workflow --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.
# Workflow Router (ors-workflow) ## When to trigger - You are starting an *Operations Research* manuscript and want the right order of operations. - You finished one stage (e.g., the optimization model is formulated) and ask "what next?" - You received a decision letter from the handling Area Editor and need to route to revision. ## What Operations Research expects *Operations Research* is the flagship methodology journal of **INFORMS**. It prizes mathematically rigorous OR/MS contributions — optimization, stochastic/probabilistic models, simulation, decision analysis — with **provable results** (theorems and proofs) alongside increasingly data-driven and applied work. Methodological novelty and rigor are valued over purely empirical work. The lifecycle below reflects OR's distinctive norms: an **equation-free introduction**, a **mandatory contribution statement** (since 1 June 2023, in the cover letter, fewer than 500 words), **area-editor routing** at submission, **soft double-anonymous** review, and the **ORJournal GitHub** code/data reproducibility workflow. ## Default order ```text ors-topic-selection (is the problem an OR/MS methodological contribution? right area?) ▼ ors-the
- When to trigger
- What Operations Research expects
- Default order
- Routing table
- The OR value arc the router protects
- Methodology-area vs. application-area routing
- Worked routing vignette (illustrative)
- Output format
What does the ors-workflow skill do?
Use as the router for an Operations Research (OR) manuscript — given where you are in the OR/MS modeling-to-submission lifecycle, it names the next ors-* skill to invoke. Routes; it does not itself formulate models (ors-theory-development), prove results (ors-methods), or run computational studies (ors-data-analysis).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-workflow --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.