Agent skill · Code Review & Quality

pom-rebuttal

Use when drafting the revision and point-by-point response after a Production and Operations Management (POM) revise-and-resubmit — addressing the Department Editor and referees, splitting changes between the main paper and the e-companion, and respecting the 32-page cap. Drafts the response after revisions; it does not interpret the decision letter (pom-review-process).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pom-rebuttal --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Production-and-Operations-Management-Skills/skills/pom-rebuttal/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

# R&R Response & Rebuttal (pom-rebuttal) ## When to trigger - You received a POM R&R and have planned (or made) the revision - You must reconcile conflicting referee demands for the Department Editor - A later-round decision asks you to defend or further revise prior changes > Write the response letter **after** revising the manuscript, not before. Resubmit through ScholarOne (mc.manuscriptcentral.com/poms) to the **same Department Editor** where possible, and keep the revised main document within the **32-page** cap — push heavy new material into the unlimited online **e-companion**. ## Response-document structure 1. **Opening letter to the Department Editor.** Thank the editor and referees; summarize the most important changes in 2–4 sentences; state explicitly how you addressed the editor's stated priorities, including any practice-relevance concern. Note where referees conflicted and how you resolved it. 2. **Per-referee sections.** Restate every comment (verbatim or faithfully numbered), then respond. 3. **Point-by-point format** for each comment: - **Comment** (quoted/numbered) - **Response** (what you changed and the OM reasoning) - **Location** (main-paper section/table/fig

What's inside
Steps it walks through
  1. When to trigger
  2. Response-document structure
  3. Responding to POM's signature demands
  4. Tone and tactics
  5. Worked micro-example: weak vs. strong response
  6. What POM referees probe, by method track
  7. Checklist
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the pom-rebuttal skill do?

Use when drafting the revision and point-by-point response after a Production and Operations Management (POM) revise-and-resubmit — addressing the Department Editor and referees, splitting changes between the main paper and the e-companion, and respecting the 32-page cap. Drafts the response after revisions; it does not interpret the decision letter (pom-review-process).

How do I install it?

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