Revision & Response for a Review (arecon-revision)
When to trigger
- A Committee/referee letter on the invited review arrived
- Referees flagged missing literatures, imbalance, mischaracterization, or "reads like a list"
- The editor asked to expand, cut, or rebalance coverage, or to make the framework explicit
- You need a point-by-point response for a review article, not a primary paper
Categories of review feedback (and how to answer each)
ARE revision asks cluster differently from primary-research asks. Triage every point into one bucket:
| Feedback type |
Typical phrasing |
Response move |
| Coverage gap |
"you omit the X literature / author Y" |
almost always concede and integrate — place the missing work in the right framework cell; re-run saturation (arecon-literature-synthesis) |
| Balance / fairness |
"this slights school Z / over-cites the author" |
steelman the slighted side; re-audit self-citation (arecon-evidence-standards) |
| Appraisal accuracy |
"you mischaracterize study W" |
correct precisely; reviewed authors often referee — fix exactly |
| Framework / structure |
"this is an annotated bibliography" |
strengthen or make explicit the spine (arecon-organizing-framework); do not just reorder paragraphs |
| Accessibility |
"a non-specialist can't follow Section 4" |
add intuition, define jargon (arecon-writing-style) |
| Scope |
"too broad / too narrow / overruns length" |
negotiate with the editor (arecon-editor-strategy); rescope deliberately, within the page envelope |
AREcon-specific revision ledger
Annual Review of Economics revisions should leave a clear economics review contract, not just a
longer bibliography. Maintain a ledger that tells the editor how each change sharpens what an
economist can learn from the review.
| Revision pressure |
Evidence to add or rebalance |
Where it should show up |
| Theory/model spine is unclear |
canonical model, mechanism, or comparative-static logic |
opening framework figure/table, section road map |
| Empirical frontier is uneven |
design map: data, identification, estimand, limitation |
evidence table and "what we know" summary |
| Magnitudes are under-interpreted |
elasticities, welfare-relevant units, or scale benchmarks |
synthesis paragraphs, not just citations |
| Field boundary is disputed |
adjacent JEL literatures and handbook/JEP-style anchors |
boundary note explaining inclusion/exclusion |
| Policy or welfare stakes are vague |
clarified mechanism-to-policy channel and uncertainty |
conclusion/agenda, with caveats preserved |
| Adjacent economists cannot follow |
intuition before notation, plain-language result labels |
section openings and table captions |
Use the ledger to prevent a common AREcon failure mode: adding every requested citation while the
review's economic proposition becomes less visible.
Writing the response letter
- Point-by-point, quote-then-respond. Reproduce each comment, then state the change and where it lives (section/page/table).
- Coverage asks: concede and integrate. A missing literature is a real defect in a review of record; adding it strengthens the article. Resist defensiveness — the omitting author may be the referee who named it.
- Balance asks: show the steelman. Demonstrate the revised text states the other side at its strongest; that is what a fairness complaint actually demands.
- Accuracy asks: fix exactly. Mischaracterizing a reviewed author who is your referee is the fastest route to a hostile second round; correct the wording precisely and, where helpful, quote their own framing.
- Translate additions into economic learning. When you add a literature, say whether it changes a
mechanism, an estimand, a benchmark magnitude, or only the historical coverage.
- Separate evidence classes. Do not let theory, calibration, quasi-experiment, structural estimate,
and descriptive trend evidence collapse into one "evidence says" paragraph.
- Disagree rarely and respectfully. If an ask would break the spine or overrun the page envelope, explain the trade-off and propose an alternative, ideally pre-cleared with the editor.
- Keep the editor central. On scope and conflicting referee asks, ask the Committee editor to adjudicate rather than satisfying mutually-incompatible referees.
- Track every addition's ripple. Adding a literature can shift the review's center of gravity; after each integration, re-check that the framework cells, the summary tables, and the balance audit still hold, and that the draft still fits the volume's length envelope.
- Mind the volume clock. Revisions run against a production deadline (
arecon-review-process); plan the rework so the article stays in its volume.
Checklist
Anti-patterns
- Defending an omission rather than adding the missing literature (a review gap is a real defect)
- Answering a balance complaint with assertions of fairness instead of revised, steelmanned text
- Dismissing or re-mischaracterizing a reviewed author who is likely your referee
- "Fixing" an annotated-bibliography critique by shuffling paragraphs without imposing a spine
- Treating theory, reduced-form evidence, structural estimates, and descriptive facts as interchangeable support
- Adding policy motivation without preserving the review's uncertainty and welfare-relevant caveats
- Bloating scope to satisfy every "also cover…" until the review overruns its length and slips the volume
- Trying to satisfy two contradictory referees instead of asking the editor to decide
Output format
【Triage】each comment bucketed (coverage/balance/appraisal/framework/accessibility/scope)? Y/N
【Coverage gaps】conceded + integrated into framework cells; saturation re-run? Y/N
【Balance】steelman shown in revised text; self-citation re-audited? Y/N
【Appraisal fixes】mischaracterizations corrected precisely? Y/N
【Framework asks】spine strengthened/made explicit (not reordered)? Y/N
【Economics ledger】theory/design/magnitude/boundary/policy stakes separated? Y/N
【Scope/length】fits page envelope + volume deadline? Y/N
【Letter】point-by-point, quote-then-respond, with locations? Y/N
【Next step】→ arecon-submission (re-deliver the revised review)
Source: brycewang-stanford/Awesome-Journal-Skills → Annual-Review-of-Economics-Skills/skills/arecon-revision/SKILL.md
1---2name: arecon-revision3description: Use when responding to Editorial Committee and referee feedback on an Annual Review of Economics (ARE) review — coverage gaps, balance/accuracy complaints, framework/structure asks, and accessibility. Drafts the response and revision plan; it does not run the delivery preflight (arecon-submission) or redesign the spine from scratch (arecon-organizing-framework).4---5
6
7# Revision & Response for a Review (arecon-revision)
8
9## When to trigger
10
11- A Committee/referee letter on the invited review arrived
12- Referees flagged missing literatures, imbalance, mischaracterization, or "reads like a list"
13- The editor asked to expand, cut, or rebalance coverage, or to make the framework explicit
14- You need a point-by-point response for a review article, not a primary paper
15
16## Categories of review feedback (and how to answer each)
17
18ARE revision asks cluster differently from primary-research asks. Triage every point into one bucket:
19
20| Feedback type | Typical phrasing | Response move |
21|---------------|------------------|---------------|
22| **Coverage gap** | "you omit the X literature / author Y" | almost always *concede and integrate* — place the missing work in the right framework cell; re-run saturation (`arecon-literature-synthesis`) |
23| **Balance / fairness** | "this slights school Z / over-cites the author" | steelman the slighted side; re-audit self-citation (`arecon-evidence-standards`) |
24| **Appraisal accuracy** | "you mischaracterize study W" | correct precisely; reviewed authors often referee — fix exactly |
25| **Framework / structure** | "this is an annotated bibliography" | strengthen or make explicit the spine (`arecon-organizing-framework`); do not just reorder paragraphs |
26| **Accessibility** | "a non-specialist can't follow Section 4" | add intuition, define jargon (`arecon-writing-style`) |
27| **Scope** | "too broad / too narrow / overruns length" | negotiate with the editor (`arecon-editor-strategy`); rescope deliberately, within the page envelope |
28
29## AREcon-specific revision ledger
30
31Annual Review of Economics revisions should leave a clear economics review contract, not just a
32longer bibliography. Maintain a ledger that tells the editor how each change sharpens what an
33economist can learn from the review.
34
35| Revision pressure | Evidence to add or rebalance | Where it should show up |
36|-------------------|------------------------------|--------------------------|
37| Theory/model spine is unclear | canonical model, mechanism, or comparative-static logic | opening framework figure/table, section road map |
38| Empirical frontier is uneven | design map: data, identification, estimand, limitation | evidence table and "what we know" summary |
39| Magnitudes are under-interpreted | elasticities, welfare-relevant units, or scale benchmarks | synthesis paragraphs, not just citations |
40| Field boundary is disputed | adjacent JEL literatures and handbook/JEP-style anchors | boundary note explaining inclusion/exclusion |
41| Policy or welfare stakes are vague | clarified mechanism-to-policy channel and uncertainty | conclusion/agenda, with caveats preserved |
42| Adjacent economists cannot follow | intuition before notation, plain-language result labels | section openings and table captions |
43
44Use the ledger to prevent a common AREcon failure mode: adding every requested citation while the
45review's economic proposition becomes less visible.
46
47## Writing the response letter
48
49- **Point-by-point, quote-then-respond.** Reproduce each comment, then state the change and where it lives (section/page/table).
50- **Coverage asks: concede and integrate.** A missing literature is a real defect in a review of record; adding it strengthens the article. Resist defensiveness — the omitting author may be the referee who named it.
51- **Balance asks: show the steelman.** Demonstrate the revised text states the other side at its strongest; that is what a fairness complaint actually demands.
52- **Accuracy asks: fix exactly.** Mischaracterizing a reviewed author who is your referee is the fastest route to a hostile second round; correct the wording precisely and, where helpful, quote their own framing.
53- **Translate additions into economic learning.** When you add a literature, say whether it changes a
54 mechanism, an estimand, a benchmark magnitude, or only the historical coverage.
55- **Separate evidence classes.** Do not let theory, calibration, quasi-experiment, structural estimate,
56 and descriptive trend evidence collapse into one "evidence says" paragraph.
57- **Disagree rarely and respectfully.** If an ask would break the spine or overrun the page envelope, explain the trade-off and propose an alternative, ideally pre-cleared with the editor.
58- **Keep the editor central.** On scope and conflicting referee asks, ask the Committee editor to adjudicate rather than satisfying mutually-incompatible referees.
59- **Track every addition's ripple.** Adding a literature can shift the review's center of gravity; after each integration, re-check that the framework cells, the summary tables, and the balance audit still hold, and that the draft still fits the volume's length envelope.
60- **Mind the volume clock.** Revisions run against a production deadline (`arecon-review-process`); plan the rework so the article stays in its volume.
61
62## Checklist
63
64- [ ] Every comment triaged into a bucket (coverage / balance / appraisal / framework / accessibility / scope)
65- [ ] Coverage gaps conceded and integrated into the right framework cell; saturation re-run
66- [ ] Balance complaints answered by demonstrable steelmanning + self-citation re-audit
67- [ ] Mischaracterizations corrected precisely (reviewed authors may be the referees)
68- [ ] "Annotated bibliography" asks answered by a stronger/explicit spine, not reordering
69- [ ] Theory, identification, magnitude, boundary, and policy/welfare stakes separated in the revision ledger
70- [ ] Accessibility fixes add intuition / define jargon for the adjacent economist
71- [ ] Scope conflicts routed to the editor; rework fits the page envelope and the volume deadline
72- [ ] Point-by-point letter: quote-then-respond, with section/page/table locations
73- [ ] Comprehensiveness + balance re-audited after all additions
74
75## Anti-patterns
76
77- Defending an omission rather than adding the missing literature (a review gap is a real defect)
78- Answering a balance complaint with assertions of fairness instead of revised, steelmanned text
79- Dismissing or re-mischaracterizing a reviewed author who is likely your referee
80- "Fixing" an annotated-bibliography critique by shuffling paragraphs without imposing a spine
81- Treating theory, reduced-form evidence, structural estimates, and descriptive facts as interchangeable support
82- Adding policy motivation without preserving the review's uncertainty and welfare-relevant caveats
83- Bloating scope to satisfy every "also cover…" until the review overruns its length and slips the volume
84- Trying to satisfy two contradictory referees instead of asking the editor to decide
85
86## Output format
87
88```text
89【Triage】each comment bucketed (coverage/balance/appraisal/framework/accessibility/scope)? Y/N
90【Coverage gaps】conceded + integrated into framework cells; saturation re-run? Y/N
91【Balance】steelman shown in revised text; self-citation re-audited? Y/N
92【Appraisal fixes】mischaracterizations corrected precisely? Y/N
93【Framework asks】spine strengthened/made explicit (not reordered)? Y/N
94【Economics ledger】theory/design/magnitude/boundary/policy stakes separated? Y/N
95【Scope/length】fits page envelope + volume deadline? Y/N
96【Letter】point-by-point, quote-then-respond, with locations? Y/N
97【Next step】→ arecon-submission (re-deliver the revised review)
98```
99
100---
101
102**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Annual-Review-of-Economics-Skills/skills/arecon-revision/SKILL.md`