Use when writing the response to a Public Administration Review (PAR) revise-and-resubmit. PAR weighs both scholarly rigor and the practitioner "so-what," so the response must convert each reviewer, satisfy the handling editor, and keep the Evidence for Practice intact. 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 pubar-rebuttal --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Pubar Rebuttal?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-pubar-rebuttal)More formats (shields.io, HTML) on the badges page.
---
name: pubar-rebuttal
description: Use when writing the response to a Public Administration Review (PAR) revise-and-resubmit. PAR weighs both scholarly rigor and the practitioner "so-what," so the response must convert each reviewer, satisfy the handling editor, and keep the Evidence for Practice intact. Structures the response letter; it does not fabricate new results.
---
# R&R Rebuttal (pubar-rebuttal)
A PAR **major or minor revision** is a real opening, but resubmission must satisfy expert
public-management reviewers **and** the handling editor — while protecting the contribution and the
**Evidence for Practice** that make the paper PAR-shaped. The response letter must move *every* reviewer
toward yes while keeping the editor confident the revision is convergent.
## When to trigger
- An R&R decision arrived and you are planning the revision + response letter
- Reviewers disagree with each other and you must reconcile their demands
- A reviewer requests analyses that would change the paper's claims or practitioner takeaways
- Writing the cover note to the editor summarizing the revision
## Strategy
1. **Read the editor's letter as the rubric.** The handling editor signals which points are decisive
and adjudicates disagreements among reviewers. 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.
3. **Concede or rebut explicitly, with evidence.** For each: did what was asked (say where, with the
new text/table number), or push back **respectfully with a reason** (theory, design, or evidence).
Editors respect a well-argued disagreement more than a hollow capitulation that weakens the paper.
4. **Reconcile conflicting reviewers openly.** When one wants the opposite of another, say so, choose a
principled path, and explain the tradeoff to the editor.
5. **Protect the contribution AND the practice bridge.** Add robustness and clarifications; resist
changes that dilute either the scholarly contribution or the honest **Evidence for Practice** that
earned the R&R. If a requested analysis weakens a practitioner takeaway, re-scope it honestly rather
than over-claim.
6. **Keep anonymity intact** in the revised manuscript (still double-blind), and **update the
transparency materials** so new tables/figures remain reproducible (see `pubar-transparency-and-data`).
## Response-letter format
For each reviewer comment:
```
> [Quoted reviewer comment]
Response: [What we did / why we respectfully disagree].
Change: [Section/page/table-figure number where the revision appears].
```
Open with a short **summary of the main changes** to the editor; group by reviewer; end each entry with
the location of every change so the editor can verify quickly.
## Triage table for a PAR R&R
| Comment signal | Who owns the call | Default move in the response |
|----------------|-------------------|------------------------------|
| Editor flags it as decisive | editor | solve first, headline it in the cover note |
| Two reviewers want opposite things | editor | pick a principled path, explain the tradeoff openly |
| Reviewer asks for an analysis that would change the claim | author + editor | run it, then defend or re-scope honestly |
| "The practitioner takeaway is over-claimed" | author | tie each Evidence-for-Practice point to a confirmatory estimate |
| "This reads like JPART/JPAM, not PAR" | author | re-anchor to public-management practice and the so-what |
## Worked micro-example (illustrative)
A hypothetical R&R draws three reviews. The editor's letter names **two** decisive points
(identification and the strength of the Evidence for Practice). R1 wants the qualitative strand **cut**;
R3 wants it **expanded**. The disciplined letter opens with a three-sentence summary to the editor,
addresses identification and the practitioner takeaways first with new text/table locations, then
reconciles R1/R3 by **keeping a compact mixed-methods integration in the main text and moving extended
interview material to the supplement** — stating the tradeoff explicitly. Of **27** total comments,
**27** receive a quoted response; **19** are conceded with a change location, **8** are rebutted with a
reason. (Counts illustrative.)
## Anti-patterns
- Ignoring or merging away a comment without a visible response
- Capitulating to a request that breaks the paper's logic or guts the Evidence for Practice
- Defensive or dismissive tone toward reviewers
- "We thank the reviewer" with no actual change or argued reason
- Letting the revised manuscript or new exhibits drift out of sync with the deposited materials
## Output format
```
【Editor's decisive points】addressed first? [list]
【Coverage】every reviewer comment answered? [Y/N]
【Concede vs rebut】each tagged with evidence + change location
【Reviewer conflicts】reconciled and explained to editor? [Y/N]
【Contribution + Evidence for Practice protected】[Y/N]
【Anonymity + transparency materials updated】[Y/N]
【Next】resubmit via the PAR portal
```
## Supplementary resources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — decision categories and editorial process
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!