# Jppm Rebuttal

> Use when executing a Journal of Public Policy & Marketing (JPP&M) revise-and-resubmit — the response letter, converting reviewer demands into analyses or studies, and defending policy claims without slipping into advocacy. Drafts the rebuttal; letter-reading and feasibility calls are jppm-review-process.

- Skill: `thedixitjain/jppm-rebuttal` (Agent Skill)
- Install (CLI): `npx skillmds add thedixitjain/jppm-rebuttal`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedixitjain/jppm-rebuttal/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: thedixitjain (https://skillmd.com/u/thedixitjain)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/thedixitjain/jppm-rebuttal

---



# Rebuttal Strategy (jppm-rebuttal)

## When to trigger

- A JPP&M major or minor revision is in hand and the response letter must be drafted
- "Strengthen the policy contribution" needs to become concrete revisions, not adjectives
- An identification critique of your DiD/RDD demands new analyses under the page cap
- A methods reviewer and a policy reviewer want opposite things
- You disagree with a comment and must push back productively

## Answer with work, weighted by the letter

The winning JPP&M response converts each substantive comment into **visible work** — a new estimator, a robustness table, a re-fielded condition, a rewritten Policy Contribution Statement — and reports the result in the letter itself, with the number. Prose-only replies persuade only on genuine matters of interpretation. Because the reviewer pool mixes camps, tailor the register: the identification reviewer gets estimates, diagnostics, and sensitivity bounds; the policy reviewer gets stakeholder mapping, institutional accuracy, and realism. Both read the whole letter, so keep every answer legible to both.

## Converting the standard JPP&M demands

| Demand | The response that closes it |
|--------|------------------------------|
| "Policy contribution is thin" | rewrite the statement around a live decision; add the decision-unit translation table; add marketer-facing implications; if the contested margin was untested, add the condition or analysis that tests it |
| "Parallel trends unconvincing" | event-study with pre-period placebos; honest-DiD sensitivity; alternative comparison group; report how conclusions move |
| "Staggered DiD concerns" | re-estimate with Callaway–Sant'Anna / Sun–Abraham; show the Bacon decomposition; reconcile with the original estimate |
| "RDD manipulation risk" | density test, donut estimates, covariate smoothness — presented together |
| "Stimuli not realistic / not mandatable" | re-field with formats from the actual rulemaking, or bound the claim explicitly to tested formats |
| "What about firm response?" | supplementary supply-side evidence (reformulation, pricing, channel shifts) or an explicit bounding argument |
| "Sample can't support vulnerability claims" | re-field with the target population, or narrow the claim and say so plainly |
| "Reads as advocacy" | recalibrate verbs, add the trade-off paragraph, report the results that cut against the recommendation |

## Structuring the letter

- **Open with the contract**: one paragraph restating the AE/editor's binding concern and the two or three biggest things the revision did about it — with headline numbers.
- **Point-by-point**: quote each comment verbatim, respond beneath it, cite the page/section/exhibit where the change lives, and excerpt new text when it settles the issue.
- **Cross-reference shared themes** once, answer fully at first occurrence, and point later instances back — reviewers notice both evasion and padding.
- **Keep the manuscript inside the 50-page cap**: state explicitly what moved to the web appendix to make room, so no one thinks material was deleted to dodge a comment.
- **Flag fact updates**: if the policy landscape shifted during review (a rule finalized, an enforcement action), update the framing and tell the reviewers you did.

## Disagreeing well

- Concede the observation before contesting the inference: "the reviewer is right that X; the data nonetheless support Y because…"
- Bring evidence to the disagreement — a supplementary analysis, an institutional citation (the statute or guidance itself), or a boundary statement.
- On institutional-accuracy disputes (what an agency can or cannot do), cite the primary source; authority questions are checkable, and being casually wrong is costly.
- If a requested revision would push the paper into advocacy or beyond the evidence, decline on exactly those grounds — editors at this journal respect calibrated refusal.
- Align every pushback with the AE's framing; never relitigate a point the AE has already adjudicated.

## Checklist

- [ ] Letter opens with the binding concern and the headline of what changed
- [ ] Every comment quoted and answered with work, location, and (where relevant) the number
- [ ] Identification comments answered with the modern-estimator battery, results reported
- [ ] Policy-contribution comments answered in the statement and implications, not just the letter
- [ ] Manuscript still ≤50 pages; web-appendix moves documented
- [ ] Disagreements evidence-based, source-cited, AE-aligned
- [ ] Landscape changes during review incorporated and flagged

## Anti-patterns

- **Adjective inflation**: strengthening the "policy contribution" with rhetoric instead of evidence or sharper mapping
- **Battery dumping**: forty unexplained robustness rows in place of the one diagnostic the reviewer asked to see
- **Camp favoritism**: satisfying the methods reviewer while the policy reviewer's realism concern festers (or vice versa)
- **Silent trimming**: cutting content to fit the cap without telling reviewers where it went
- **Stale landscape**: resubmitting with framing the intervening rulemaking has overtaken
- **Relitigating the AE**: fighting a settled point in round two

## Output format

```text
【Binding concern】restated in one line + what the revision did about it
【Work ledger】comment → analysis/study/reframe → result (with numbers) → manuscript location
【Camp balance】methods asks and policy asks both closed? [Y/N]
【Page cap】≤50 pages after additions; appendix moves listed
【Disagreements】where, on what evidence, AE-aligned
【Next step】resubmit via mc.manuscriptcentral.com/ama_jppm; if rejected, jppm-review-process to reroute
```

---

**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-rebuttal/SKILL.md`