sf-rebuttal

star 39

Use when writing the response to a Social Forces (SF) revise-and-resubmit. SF reviewers prize methodological rigor and general significance, and most published papers go through at least one R&R, so the response must convert each reviewer without alienating the editor — all while keeping the revision within the reference-inclusive 10,000-word and 10-panel limits. Structures the response letter; it does not fabricate new results.

brycewang-stanford By brycewang-stanford schedule Updated 6/12/2026

name: sf-rebuttal description: Use when writing the response to a Social Forces (SF) revise-and-resubmit. SF reviewers prize methodological rigor and general significance, and most published papers go through at least one R&R, so the response must convert each reviewer without alienating the editor — all while keeping the revision within the reference-inclusive 10,000-word and 10-panel limits. Structures the response letter; it does not fabricate new results.

R&R Rebuttal (sf-rebuttal)

A Social Forces R&R is the normal road to publication — most accepted papers pass through one. The response letter must move every reviewer toward yes while keeping the editor confident the revision is convergent. The SF-specific twist: each new analysis or paragraph you add must still fit the 10,000-word cap (references included) and the 10 tables-and-figure-panels limit, so you often trade content rather than simply add it.

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 push you over the word or panel limits
  • Writing the cover note to the editor summarizing the revision

Strategy

  1. Read the editor's letter as the rubric. The editor signals which points are decisive. Solve those first; the editor adjudicates disagreements among reviewers.
  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/panel number), or push back respectfully with a reason (theory, design, or evidence). A well-argued disagreement beats a hollow capitulation that weakens the paper.
  4. Reconcile conflicting reviewers openly. When R2 wants the opposite of R3, say so, choose a principled path, and explain the tradeoff to the editor.
  5. Mind the budget when you add. New robustness tables count against the 10-panel limit; new prose and citations count against the reference-inclusive 10,000-word cap. Move supporting material to the supplementary file (≤ 10 pages) and consolidate exhibits (see sf-tables-figures, sf-writing-style).
  6. Protect the contribution and the rigor. Add checks that strengthen credibility; resist changes that dilute the general-significance claim that earned the R&R. Keep the revision anonymized and update the data availability statement / materials so new exhibits remain reproducible (see sf-data-and-transparency).

Response-letter format

For each reviewer comment:

> [Quoted reviewer comment]

Response: [What we did / why we respectfully disagree].
Change: [Section/page/table-figure-panel 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. Note where added material went to the supplement to stay within the word and panel caps.

Anti-patterns

  • Ignoring or merging away a comment without a visible response
  • Adding so much that the revision blows the 10,000-word (incl. refs) or 10-panel limits
  • Capitulating to a request that breaks the paper's logic just to please a reviewer
  • Defensive or dismissive tone toward reviewers
  • Letting the revised manuscript or new exhibits drift out of sync with the declared data/code

Triaging reviewer demands against the SF budget

Because an SF R&R must still land within the reference-inclusive 10,000-word cap and the 10-panel limit, every requested addition is a budget decision. Sort demands before drafting:

Reviewer demand Default response Budget handling
Editor's decisive point Address fully, first Spend words/panels here first
Reasonable robustness check Run it Summary panel in text; grid to supplement
Conflicting R2 vs R3 Pick a principled path Avoid doubling content to please both
Out-of-scope expansion Reasoned pushback Protect the contribution and the cap

Calibration (hedged): most published SF papers pass through at least one R&R; treat decision categories as reported norms to confirm against current guidelines.

Worked vignette (illustrative)

A neighborhoods-and-attainment R&R: R1 wants a falsification test, R2 wants a long mechanisms section, R3 calls a control "post-treatment." The editor flagged identification as decisive, so both fixes go in the main text — the new test becomes one panel, replacing a now-redundant robustness table to stay at 10. R2's request gets a tightened passage plus a supplementary analysis, not a section that blows the cap.

Referee fixes: "you ignored my comment" → quote and answer every one; "over length" → move detail to the supplement.

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]
【Budget after revision】≤ 10,000 words (incl. refs) and ≤ 10 panels? [Y/N]
【Anonymity + data statement updated】[Y/N]
【Next】resubmit via ScholarOne

Supplementary resources

Install via CLI
npx skills add https://github.com/brycewang-stanford/Awesome-Journal-Skills --skill sf-rebuttal
Repository Details
star Stars 39
call_split Forks 11
navigation Branch main
article Path SKILL.md
More from Creator
brycewang-stanford
brycewang-stanford Explore all skills →