orgsci-review-process
Use when you want to understand how Organization Science review and decisions work before or after submitting — the decentralized senior-editor model with strong SE autonomy, the conflict-of-interest routing cascade, double-blind submission preparation, and how to read a decision letter at this venue.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-review-process --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.
# Review Process (orgsci-review-process) ## When to trigger - You are about to submit and want to set expectations - You received a decision letter and need to interpret who decided and why - You are unsure how Organization Science routing differs from a departmental area-editor journal ## The decentralized senior-editor model Organization Science runs a **decentralized model**: **Senior Editors** plus an **Editorial Review Board**, under Editor-in-Chief **Lamar Pierce** (Washington University in St. Louis). Each **Senior Editor has strong autonomy** — an SE can independently **accept, reject, or request an R&R**. This differs sharply from sister journal Management Science's fixed **departmental area-editor** routing: here the SE decides your paper, not a department head dispatching to an area editor. Routing follows a **conflict-of-interest cascade** — the **EIC handles deputy-editor submissions** and **deputy editors handle senior-editor submissions** — so editors do not adjudicate their own work. ## What happens to your submission - **Desk review.** The EIC/SE can see the cover letter and abstract. An unconvincing contribution, poor fit, transparency gap, or excessive length can
- When to trigger
- The decentralized senior-editor model
- What happens to your submission
- Reading the decision letter
- Anti-patterns
- Review-risk pass for Organization Science
- Output format
What does the orgsci-review-process skill do?
Use when you want to understand how Organization Science review and decisions work before or after submitting — the decentralized senior-editor model with strong SE autonomy, the conflict-of-interest routing cascade, double-blind submission preparation, and how to read a decision letter at this venue.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-review-process --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.