Skip to content

brycewang-stanford/Auto-Empirical-Research-Skills / skills/41-sticerd-eee-sewage-econometrics-check/skills/respond-to-referee

respond-to-referee

Verified

Structure point-by-point referee responses for the sewage-house-prices paper. Classifies each comment (NEW ANALYSIS / CLARIFICATION / REWRITE / DISAGREE / MINOR), produces a tracking document, drafts a response letter in LaTeX, and flags items needing new analysis or user judgment. This skill should be used when asked to "respond to referees", "draft revision", "address referee comments", or "R&R".

Respond to Referee

Structure a point-by-point response to referee reports for the sewage-house-prices manuscript.

Input: $ARGUMENTS — path to referee report file(s).


Project-Specific Context

Manuscript

  • Main document: docs/overleaf/_main.tex
  • Sections: docs/overleaf/*.tex
  • Bibliography: docs/overleaf/refs.bib

Analysis

  • Scripts: scripts/R/09_analysis/
  • Tables: output/tables/
  • Figures: output/figures/

Common Referee Concerns for This Paper

  • Short EDM panel (2021-2024) — limited time variation
  • LSOA FE may not capture neighbourhood-level sorting
  • Spill count vs hours as treatment — which matters more?
  • External validity beyond England
  • Dry spill identification — rainfall threshold sensitivity
  • Multiple testing across 6 radii and multiple specifications

Workflow

Step 1: Parse Inputs

  1. Read referee report(s) from $ARGUMENTS
  2. Read the manuscript (docs/overleaf/_main.tex and section files)
  3. Scan existing analysis scripts to know what already exists

Step 2: Classify Every Comment

Assign each referee point a classification:

ClassAction
NEW ANALYSISFlag for user — requires new R script or specification
CLARIFICATIONDraft revised text for the relevant section
REWRITEDraft structural revision of a section
DISAGREEDraft diplomatic pushback — flag for user review (mandatory)
MINORDraft fix directly (typos, formatting, minor edits)

Step 3: Build Tracking Document

Save to output/log/referee_response_tracker.md:

# Referee Response Tracker
**Date:** YYYY-MM-DD
**Journal:** [if known]
**Decision:** [R&R / Major / Minor]

## Summary
- Referee 1: N comments (X new analysis, Y clarification, Z disagree, W minor)
- Referee 2: N comments (...)
- Editor: N comments (...)
- **Total new analyses required:** X

## Action Items (Priority Order)

### HIGH: New Analysis Required
| # | Ref | Point | Status |
|---|-----|-------|--------|
| 1 | R1.3 | [Brief] | TODO |

### MEDIUM: Clarification / Rewriting
| # | Ref | Point | Status |
|---|-----|-------|--------|
| 1 | R1.1 | [Brief] | TODO |

### FLAGGED: Disagreements (require user review)
| # | Ref | Point | Draft Response |
|---|-----|-------|---------------|
| 1 | R2.5 | [Brief] | [Draft] |

### LOW: Minor Edits
- [ ] R1.7: Fix typo on p. 12

Step 4: Draft Response Letter

Generate LaTeX response letter:

\documentclass[12pt]{article}
\usepackage[margin=1in]{geometry}
\usepackage{xcolor}
\definecolor{response}{RGB}{0,0,128}

\begin{document}

\title{Response to Referee Reports: Sewage in Our Waters}
\author{[Authors]}
\date{\today}
\maketitle

Dear Editor,

We thank the editor and referees for their careful and constructive comments.
We have revised the manuscript to address all points raised.

\bigskip

\textbf{Summary of major changes:}
\begin{enumerate}
\item [Major change 1 — addresses R1.3, R2.1]
\item [Major change 2 — addresses R1.5]
\end{enumerate}

\newpage
\section*{Response to Referee 1}

\subsection*{Comment 1.1}
\textit{[Exact quote of referee comment]}

\medskip
\textcolor{response}{%
\textbf{Response:} [Draft response]

\textbf{Paper change:} [Section X, page Y]
}

\end{document}

Save to output/log/referee_response_[date].tex.

Step 5: Diplomatic Disagreement Protocol

When classification is DISAGREE:

  1. Open with acknowledgment of the referee's point
  2. Provide specific evidence (data, results, published work)
  3. Offer partial concession where possible
  4. Never say: "The referee is wrong" or "misunderstood"
  5. Instead say: "We respectfully note...", "Upon reflection, we believe..."
  6. FLAG prominently for user review

Principles

  • The response letter is the authors' voice. Match their academic tone.
  • Never fabricate results. Mark NEW ANALYSIS items as TBD until implemented.
  • Flag all DISAGREE items. These need human judgment — never resolve disagreements autonomously.
  • Prioritize editor's comments. The editor signals which concerns matter most.
  • Track everything. Every referee comment appears in both tracker and response letter.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall