Use when writing the response to a Governance: An International Journal of Policy, Administration, and Institutions revise-and-resubmit. The response must convert each of the ≥ 2 referees and the editor, answering comparative-reviewer concerns (case selection, generalizability across countries, measurement of institutions, alternative institutional explanations) point by point. Structures the response letter; it does not fabricate new results.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill govern-rebuttal --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Govern Rebuttal?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-govern-rebuttal)More formats (shields.io, HTML) on the badges page.
---
name: govern-rebuttal
description: Use when writing the response to a Governance: An International Journal of Policy, Administration, and Institutions revise-and-resubmit. The response must convert each of the ≥ 2 referees and the editor, answering comparative-reviewer concerns (case selection, generalizability across countries, measurement of institutions, alternative institutional explanations) point by point. Structures the response letter; it does not fabricate new results.
---
# R&R Rebuttal (govern-rebuttal)
A *Governance* **R&R** means at least two referees and the editor see a real comparative/institutional
contribution worth saving. It is an invitation, not an acceptance. The response letter must move *every*
referee toward yes while keeping the editor confident the revision is convergent — and at this journal
the recurring battleground is whether the claim **travels across countries and institutions**, so the
letter has to defend or honestly re-scope the comparative reach, not retreat to a single-country result.
## When to trigger
- An R&R decision arrived and you are planning the revision + response letter
- Referees disagree with each other and you must reconcile their demands
- A referee requests analyses (more cases, different institutional measures) that could change the claim
- Writing the cover memo to the editor summarizing the revision
## Strategy
1. **Read the editor's letter as the rubric.** The editor signals which points are decisive and
adjudicates disagreements among referees. Solve those first.
2. **One point-by-point response, every comment addressed.** Quote each comment, then respond. Never
skip one — silence reads as non-compliance to a referee who must be won over.
3. **Concede or rebut explicitly, with evidence.** For each comment: did what was asked (say where, with
the new text/table/figure number), or push back **respectfully with a reason** grounded in theory,
design, or evidence. A well-argued disagreement earns more respect than a hollow capitulation that
weakens the comparative claim.
4. **Reconcile conflicting referees openly.** When R1 wants more cases and R2 wants a deeper single-case
process trace, say so, choose a principled path, and explain the tradeoff to the editor rather than
silently satisfying one.
5. **Protect the contribution.** Add robustness and clarifications; resist changes that dilute the
comparative/institutional reach that earned the R&R. Defend scope conditions rather than over-claiming.
6. **Keep anonymity intact** in the revised manuscript (still double-blind), and **update the replication
materials and the Data Availability Statement** so new exhibits remain reproducible (see
`govern-transparency-and-data`).
## Comparative-reviewer concerns: concede vs defend
| Comment signal | Who owns the call | Default move in the response |
|----------------|-------------------|------------------------------|
| Editor flags it as decisive | editor | solve first, headline it in the cover memo |
| "Why these countries/cases?" (selection) | author + editor | justify the sample on inferential grounds; if selected on outcome, fix or re-scope and say so |
| "Does it generalize beyond these cases?" | author | state scope conditions honestly; add cases/tests if feasible, do not over-claim |
| "Your institutional measure isn't comparable across cases" | author | defend the operationalization or add an alternative measure; show robustness |
| "You ignored an alternative institutional explanation" | author | run/discuss the rival account and show why yours survives |
| Two referees want opposite things | editor | pick a principled path, explain the tradeoff openly |
Concede readily on measurement robustness, added rival tests, and clarifications. Defend — with reasons —
the core comparative framing, defensible case selection, and honestly bounded scope conditions.
## Response-letter format
For each referee comment:
```
> [Quoted referee comment]
Response: [What we did / why we respectfully disagree].
Change: [Section/page/table-figure number where the revision appears].
```
Open with a short **cover memo to the editor** summarizing the main changes (lead with the editor's
decisive points), then group responses by referee, ending each entry with the location of the change so
the editor can verify quickly.
## Checklist
- [ ] Editor's decisive points identified and solved first; headlined in the cover memo
- [ ] Every referee comment quoted and answered (no silent merges)
- [ ] Each response tagged: conceded (with change location) or rebutted (with a reason)
- [ ] Case-selection, generalizability, and institutional-measurement concerns addressed head-on
- [ ] Conflicting referees reconciled with a principled, openly explained tradeoff
- [ ] Comparative/institutional reach protected — no retreat to a parochial single-country result
- [ ] Revised manuscript still double-blind; replication materials + Data Availability Statement updated
## Anti-patterns
- Ignoring or merging away a comment without a visible, quoted response
- Retreating to a single-country result to dodge a generalizability comment (kills the contribution)
- Capitulating to a request that breaks the paper's logic just to please a referee
- Defensive or dismissive tone toward referees
- Adding cases/analyses that quietly contradict the original claim without acknowledging it
- Letting the revised manuscript or new exhibits drift out of sync with the replication materials
## Worked micro-example (illustrative)
A hypothetical R&R draws three reviews. The editor names **two** decisive points (case selection and the
comparability of the state-capacity measure). R1 wants two more countries added; R2 wants the existing
cases traced in more depth. The disciplined letter opens with a three-sentence memo to the editor,
addresses case selection and measurement first with new text/table locations, then reconciles R1/R2 by
**adding one well-justified case and deepening the process trace for the two original cases** — stating
the tradeoff openly rather than silently siding with one referee. Of **27** total comments, **27** receive
a quoted response; **19** are conceded with a change location, **8** are rebutted with a reason. (Counts
illustrative.)
## Output format
```
【Editor's decisive points】addressed first? [list]
【Coverage】every referee comment answered? [Y/N]
【Concede vs rebut】each tagged with evidence + change location
【Comparative reach protected】no retreat to a parochial single-country result? [Y/N]
【Referee conflicts】reconciled and explained to editor? [Y/N]
【Anonymity + materials/DAS updated】[Y/N]
【Next】resubmit via govern-submission (or govern-review-process for the next round)
```
## Supplementary resources
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — added-analysis and robustness tooling for the revision
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — *Governance* decision categories and resubmission policy
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!