Use when revising a Journal of the American Academy of Religion (JAAR) article after a revise-and-resubmit and writing the response to readers' reports. Reviewers come from different traditions and methods, so the response must satisfy each on its own terms while protecting the article's argument and its broad significance. Plans the revision and response; it does not fabricate sources.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jaar-revision-and-response --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Jaar Revision And Response?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-jaar-revision-and-response)More formats (shields.io, HTML) on the badges page.
---
name: jaar-revision-and-response
description: Use when revising a Journal of the American Academy of Religion (JAAR) article after a revise-and-resubmit and writing the response to readers' reports. Reviewers come from different traditions and methods, so the response must satisfy each on its own terms while protecting the article's argument and its broad significance. Plans the revision and response; it does not fabricate sources.
---
# Revision & Response (jaar-revision-and-response)
A JAAR **R&R** is a genuine opening at a journal that rejects ~90%. But the readers may come from very
different corners of the study of religion (a textual scholar, a theorist, an ethnographer), and they
will ask for different things. The response letter must answer each report on its own terms while
keeping the **argument** and its **broad significance** intact — and the revision stays double-blind.
## When to trigger
- An R&R / revise decision arrived and you are planning the revision + response letter
- Readers' reports pull in different methodological directions
- A reader asks for engagement with a literature or source base that would reshape the article
- Writing the cover note to the editor
## Strategy
1. **Read the editor's letter as the rubric.** The editor distills which points are decisive; address
those first. The editor — not any single reader — adjudicates.
2. **Point-by-point, every comment.** Quote or paraphrase each reader comment, then respond; do not skip
any, even ones you decline.
3. **Concede or reply with reasons.** Where a reader is right, revise and say where (section/page);
where you disagree, make the scholarly case (evidence, method, or framing) — a well-argued reply
beats a capitulation that weakens the argument.
4. **Reconcile cross-method readers.** When a textual reader and a theorist want different emphases,
choose a principled path that keeps the essay coherent **in its own method**, and explain the
tradeoff to the editor rather than trying to be every kind of article at once.
5. **Protect broad significance.** Many R&Rs push toward more specialist detail; add it where it
strengthens the argument, but do not let the article slide back into a subfield-only piece (the very
thing JAAR screens against). Keep the field-level stakes front and center.
6. **Keep it submittable.** Maintain anonymity in the revised main document (third-person self-cites);
keep in-text author-date citations; respect the word budget as notes grow.
## Response-letter format
For each reader comment:
```
> [Quoted / paraphrased reader comment]
Response: [What we revised / why we respectfully disagree, with the scholarly reason].
Change: [Section/page where the revision appears].
```
Open with a brief note to the editor summarizing the main changes and how the revision preserves the
article's broad significance; group by reader; end each entry with the change location.
## Anti-patterns
- Ignoring or quietly merging away a comment
- Capitulating to a request that erodes the argument or its field-level significance
- Over-specializing the revision until it no longer reads for the whole field
- Defensive or dismissive tone toward readers
- Letting anonymity or in-text citation style lapse in the revised file
## Output format
```
【Editor's decisive points】addressed first? [list]
【Coverage】every reader comment answered? [Y/N]
【Concede vs reply】each tagged with scholarly reason + change location
【Cross-method conflicts】reconciled and explained to editor? [Y/N]
【Broad significance protected】not narrowed to a subfield? [Y/N]
【Anonymity + in-text citations intact】[Y/N]
【Next】resubmit via Manuscript Central
```
## Supplementary resources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — review model and decision categories
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!