popdevr-rebuttal
GitHub针对人口与发展评论期刊R&R决定的回复信生成技能。指导如何协调跨领域审稿人意见，结构化回应编辑与专家质疑，通过证据论证保护研究贡献，确保双盲匿名及APA格式合规，提升稿件录用率。
Trigger Scenarios
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popdevr-rebuttal -g -y
SKILL.md
Frontmatter
{
"name": "popdevr-rebuttal",
"description": "Use when writing the response to a Population and Development Review (PDR, Wiley \/ Population Council) revise-and-resubmit. PDR review is double-anonymized and cross-field (demographers and development scholars), so the response must convert every expert reviewer on population substance and on the development meaning, without alienating the editor. Structures the response letter; it does not fabricate new results."
}
R&R Rebuttal (popdevr-rebuttal)
A PDR R&R is a real opportunity — editors and referees thought the population-and-development contribution is worth saving. But the editor decides, and the referees are cross-field (a demographer and a development/policy scholar may have reviewed the same paper from different angles), so the response letter must move every reviewer toward yes on both the population substance and its development meaning 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 (e.g., a demographer questions the rate construction while a development referee questions the causal/policy claim) and you must reconcile them
- A reviewer requests analyses (a re-decomposition, a sensitivity, an alternative projection, a comparability check) that could change the claims
- Writing the cover note to the editor summarizing the revision
Strategy
- Read the editor's letter as the rubric. It signals which points are decisive — often the fit, the identification, or the development/policy framing. Solve those first; the editor adjudicates disagreements among reviewers.
- One point-by-point response, every comment addressed. Quote each comment, then respond. Never skip one — silence reads as non-compliance.
- Concede or rebut explicitly, with evidence. For each: did what was asked (say where, with the new table/figure number), or push back respectfully with a reason grounded in demographic method or the development logic (why the chosen rate, decomposition, or framing is appropriate). Editors respect a well-argued disagreement more than a capitulation that weakens the paper.
- Reconcile cross-field reviewers openly. When the demographer and the development referee pull in different directions, say so, choose a principled path, and explain the tradeoff. Don't silently satisfy one and ignore the other.
- Protect the contribution. Add robustness (alternative exposures, sensitivity, comparability checks, alternative projections) and clarifications; resist changes that dilute the population-and-development claim or flatten a synthetic essay into a literature summary. Defend scope conditions rather than over-claiming.
- Keep anonymity intact in the revised manuscript (still double-anonymized), apply the APA-style
house formatting now that Free Format's first round is over, and update the data availability
statement and reproducibility materials so new exhibits remain reproducible (see
popdevr-transparency-and-data).
Cross-field response ledger
Build a ledger before drafting prose. PDR revisions often fail when the response satisfies one expert audience while leaving the other unconvinced.
| Comment type | Demographic evidence | Development/policy evidence | Response posture |
|---|---|---|---|
| Rate, denominator, exposure, or population-at-risk concern | alternative rate construction, exposure definition, cohort/person-period logic | explains how the population measure changes the development interpretation | usually concede with a new table or appendix |
| Comparability across countries, periods, or subgroups | harmonization note, sensitivity to definitions, uncertainty by group | states what comparison can and cannot support for policy inference | concede partly; narrow the claim if needed |
| Causal or selection concern | robustness, falsification, decomposition, or scope condition | separates development meaning from causal overreach | add evidence where feasible; soften verbs where not |
| Synthetic essay lacks contribution | framework boundary, typology, or mechanism clarified | policy/development stakes and cases made explicit | rewrite framing, not only add citations |
| Reviewer asks for too much expansion | explains why the requested population analysis would break focus | explains why the development claim remains bounded without it | respectful pushback plus future-work note |
For each row, assign: concede, concede partly, rebut, or defer, and name the manuscript
location where the change appears. No row should end with only "clarified in text" unless the issue is
purely expository.
Conflict-resolution note to the editor
When reviewers pull in different directions, write the tradeoff explicitly in the cover note instead of hiding it inside point-by-point responses.
R1 requested a finer age-specific decomposition, while R2 asked us to foreground the cross-national
development implication. We added the decomposition as Appendix Table A3 and use the main text to
state the policy interpretation more narrowly. This preserves the demographic logic without widening
the development claim beyond the evidence.
Use this pattern whenever one request would make the paper longer, narrower, more technical, or less development-facing than another request. The editor should see that the revision is convergent.
Claim-change control
Every new analysis should be tied to a claim decision.
| New material | Claim decision |
|---|---|
| Robustness confirms the original result | keep claim, add precision and uncertainty |
| Robustness weakens magnitude but keeps direction | narrow magnitude language and update abstract/discussion |
| Alternative denominator changes interpretation | revise the population mechanism, not just a footnote |
| Development implication no longer follows | move claim to scope condition or future research |
| Reviewer-requested expansion is infeasible | explain why, add the nearest feasible check, and avoid pretending it was done |
After revisions, re-read the abstract, introduction, conclusion, tables, and response letter together. They must tell the same story about what changed.
Response-letter format
For each reviewer comment:
> [Quoted reviewer comment]
Response: [What we did / why we respectfully disagree, on demographic or development grounds].
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 and referees can verify quickly.
Anti-patterns
- Ignoring or merging away a comment without a visible response
- Capitulating to a request that breaks the demographic logic (e.g., a wrong denominator change) or the development argument just to please a reviewer
- Defensive or dismissive tone toward expert cross-field reviewers
- "We thank the reviewer" with no actual change or argued reason
- Satisfying the demographer while ignoring the development referee (or vice versa)
- Letting the revised manuscript or new exhibits drift out of sync with the deposited materials
Output format
【Editor decisive points】addressed first? [list]
【Coverage】every reviewer comment answered? [Y/N]
【Concede vs rebut】each tagged with demographic/development evidence + change location
【Cross-field conflicts】reconciled and explained to editor? [Y/N]
【Contribution protected】no dilution of the population-and-development claim? [Y/N]
【Claim changes】kept / narrowed / reframed / deferred, with locations
【Materials sync】new exhibits reflected in DAS, appendix, and reproducibility files? [Y/N]
【Anonymity + APA formatting + materials updated】[Y/N]
【Next】resubmit via ScholarOne
Supplementary resources
../../resources/official-source-map.md— review-process, double-anonymized, and revision policy
Version History
- 1839142 Current 2026-07-05 14:12
