Cell Rebuttal

---
name: cell-rebuttal
description: Use after Cell reviews arrive to triage the decision, prioritize the (often substantial) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the "completeness" gaps reviewers demand. Do not run before the experiments and revision are actually done.
---

# Reviewer Rebuttal (cell-rebuttal)

## When to trigger

- A decision letter arrives (reject / reject-but-resubmit / major or minor revision).
- You have reviewer comments and need a strategy before running experiments.
- A revision is drafted and you need the point-by-point response letter.

## What's distinctive about Cell reviews

Cell reviews are typically **detailed and demanding**, and frequently request **substantial new experiments** to make the story **airtight**. The recurring theme is **completeness**: reviewers push for the mechanism to be fully nailed down, alternatives excluded, and causality proven. Expect to do real bench work, not just rewriting.

## Step 0: read the editor's letter first

The **editor's** framing **outranks** individual reviewers. Identify:

- The decision type and whether a new review round is implied.
- Which concerns the editor **emphasizes** (load-bearing — address fully).
- Any **deal-breaker** the editor names (e.g., "the central mechanism needs an independent line of evidence").

> The editor often signals which reviewer requests are essential versus optional. Weight the response accordingly — do not treat all three reviewers as equal if the editor has prioritized.

## Triage every comment into 4 buckets

| Bucket             | Action                                                            |
|--------------------|------------------------------------------------------------------|
| **Do** (fair, feasible) | Run the experiment / make the change; show it; quote the new figure. |
| **Do-partial**     | Do what's feasible; explain the boundary with evidence.          |
| **Defend** (wrong/out of scope) | Push back respectfully, with data/citations — not assertion. |
| **Defer** (future work) | Acknowledge; add a sentence to the text; don't over-promise. |

Most rejections-on-revision come from **silently skipping** a load-bearing comment or **defending** when an experiment was actually required to complete the story.

## Prioritize the experiments (impact × feasibility)

- Rank requested experiments by **(impact on the central mechanism) × (feasibility/time)**.
- The reviewer's #1 concern about the **core mechanism** must be answered with **data**, not prose — this is where Cell's completeness demand bites hardest.
- Cluster overlapping requests from different reviewers into one decisive experiment where possible.
- If an experiment is infeasible, offer the **strongest orthogonal evidence** and explain why it closes the gap.
- Sequence long experiments early; don't let one assay become the critical path to resubmission.

## Response-letter format

For each comment:

```
Reviewer N, Comment k: <verbatim quote of the reviewer>

Response: <what we did / our reasoning>. <Evidence: new Figure/panel, statistics.>
Changes: "<quoted new manuscript text>" (Results, p. X; new Figure Sk; STAR Methods).
```

- Open with a short thank-you and a 3–4 line summary of the **major changes / new experiments** across the whole revision.
- Quote each comment **verbatim**; never paraphrase a reviewer in a way that softens their point.
- **Quote the new manuscript text and name the new figures** so the editor can verify without hunting.
- Use a consistent visual convention (reviewer text plain; your response indented; manuscript quotes in italics/color).

## The "completeness" demand (Cell-specific)

When a reviewer says the story is "incomplete" or "the mechanism is not established," this is the **most load-bearing** comment for a Cell paper. Either:
- add the experiment(s) that make the mechanism airtight (loss + gain of function, an orthogonal technique, in vivo confirmation), or
- **narrow the claim** so the conclusion matches the evidence — and re-check `cell-fit`, because a narrowed claim may now fit Cell Reports better.

## Tone rules

- Respectful and non-defensive, even when the reviewer misread the paper — if they misread it, the writing was unclear; fix the writing **and** explain.
- Concede real limitations explicitly; an honest limitation builds credibility.
- No sarcasm, no "as we clearly stated"; assume good faith.

## Output format

```
【Decision type】 reject / reject-resubmit / major / minor
【Editor's load-bearing concerns】 [...]
【Deal-breaker】 ... → plan to resolve
【Comment triage】 Do [...] / Do-partial [...] / Defend [...] / Defer [...]
【Experiment priority】 ranked by impact × feasibility; critical path noted
【Completeness gap】 mechanism airtight? else add experiment / narrow claim (→ cell-fit)
【Response letter】 drafted point-by-point with quoted changes + new figures
```

## Anti-patterns

- **Do not** silently skip a comment the editor emphasized.
- **Do not** defend by assertion where the reviewer asked for an experiment.
- **Do not** over-promise future work to dodge a needed experiment.
- **Do not** draft the response before the experiments and revision are actually done.

> Confirm revision format and deadlines against the decision letter and current Cell Press guidelines.