Workflow 4: Rebuttal
Before each reviewer slot, follow Selectable Reviewers:
resolve invocation → .aris/reviewer.json → Codex default (fresh native reviewer)
with reviewer_route.py through the canonical helper resolver, preserving this
slot's tier, fresh contexts, source/image inputs and deterministic gates.
Codex examples/pins below apply only to backend=codex; other routes use their
own first-call/reply contract. Save the route and actual returned identity;
unavailable selections are REVIEW_UNAVAILABLE. Classify acceptance from actual
families/completion/scope. Forward invocation reviewer/model/effort overrides
to reviewer-bearing children. Generation workers are unchanged.
Prepare and maintain a grounded, venue-compliant rebuttal for: $ARGUMENTS
Scope
This skill is optimized for:
- ICML-style text-only rebuttal
- strict character limits
- multiple reviewers
- follow-up rounds after the initial rebuttal
- safe drafting with no fabrication, no overpromise, and full issue coverage
This skill does not:
- run new experiments automatically
- generate new theorem claims automatically
- edit or upload a revised PDF
- submit to OpenReview / CMT / HotCRP
If the user already has new results, derivations, or approved commitments, the skill can incorporate them as user-confirmed evidence.
Lifecycle Position
Workflow 1: idea-discovery
Workflow 1.5: experiment-bridge
Workflow 2: auto-review-loop (pre-submission)
Workflow 3: paper-writing
Workflow 4: rebuttal (post-submission external reviews)
Constants
- VENUE =
ICML — Default venue. Override if needed.
- RESPONSE_MODE =
TEXT_ONLY — v1 default.
- REVIEWER_MODEL =
gpt-6-astra — Used via Codex MCP for internal stress-testing.
- REVIEWER_BACKEND =
codex — Default: Codex xhigh stress tester. Use --reviewer: oracle-pro only when explicitly requested; if Oracle is unavailable, warn and fall back to Codex xhigh. See ../shared-references/reviewer-routing.md.
- MAX_INTERNAL_DRAFT_ROUNDS = 2 — draft → lint → revise.
- MAX_STRESS_TEST_ROUNDS = 1 — One Codex MCP critique round.
- MAX_FOLLOWUP_ROUNDS = 3 — per reviewer thread.
- AUTO_EXPERIMENT = false — When
true, automatically invoke /experiment-bridge to run supplementary experiments when the strategy plan identifies reviewer concerns that require new empirical evidence. When false (default), pause and present the evidence gap to the user for manual handling.
- QUICK_MODE = false — When
true, only run Phase 0-3 (parse reviews, atomize concerns, build strategy). Outputs ISSUE_BOARD.md + STRATEGY_PLAN.md and stops — no drafting, no stress test. Useful for quickly understanding what reviewers want before deciding how to respond.
- REBUTTAL_DIR =
rebuttal/
- RENDER_HTML = true — When
true (default), auto-render rebuttal/REBUTTAL_DRAFT_rich.md to HTML after Phase 6 / Phase 8 finalization via /render-html. Uses full review gate (reviewer-facing pre-submission deliverable). The plain-text PASTE_READY.txt is NOT rendered (it's character-counted plain text by design). Set false to skip, or pass — render html: false. Non-blocking: failures don't invalidate the rebuttal.
Override: /rebuttal "paper/" — venue: NeurIPS, character limit: 5000
Required Inputs
- Paper source — PDF, LaTeX directory, or narrative summary
- Raw reviews — pasted text, markdown, or PDF with reviewer IDs
- Venue rules — venue name, character/word limit, text-only or revised PDF allowed
- Current stage — initial rebuttal or follow-up round
If venue rules or limit are missing, stop and ask before drafting.
Safety Model
Three hard gates — if any fails, do NOT finalize:
- Provenance gate — every factual statement maps to:
paper, review, user_confirmed_result, user_confirmed_derivation, or future_work. No source = blocked.
- Commitment gate — every promise maps to:
already_done, approved_for_rebuttal, or future_work_only. Not approved = blocked.
- Coverage gate — every reviewer concern ends in:
answered, deferred_intentionally, or needs_user_input. No issue disappears.
Workflow
Phase 0: Resume or Initialize
- If
rebuttal/REBUTTAL_STATE.md exists → resume from recorded phase
- Otherwise → create
rebuttal/, initialize all output documents
- Load paper, reviews, venue rules, any user-confirmed evidence
Phase 1: Validate Inputs and Normalize Reviews
- Validate venue rules are explicit
- Normalize all reviewer text into
rebuttal/REVIEWS_RAW.md (verbatim)
- Record metadata in
rebuttal/REBUTTAL_STATE.md
- If ambiguous, pause and ask
Phase 2: Atomize and Classify Reviewer Concerns
Create rebuttal/ISSUE_BOARD.md.
For each atomic concern:
issue_id (e.g., R1-C2)
reviewer, round, raw_anchor (short quote)
issue_type: assumptions / theorem_rigor / novelty / empirical_support / baseline_comparison / complexity / practical_significance / clarity / reproducibility / other
severity: critical / major / minor
reviewer_stance: positive / swing / negative / unknown
response_mode: direct_clarification / grounded_evidence / nearest_work_delta / assumption_hierarchy / narrow_concession / future_work_boundary
status: open / answered / deferred / needs_user_input
Phase 3: Build Strategy Plan
Create rebuttal/STRATEGY_PLAN.md.
- Identify 2-4 global themes resolving shared concerns
- Choose response mode per issue
- Build character budget (10-15% opener, 75-80% per-reviewer, 5-10% closing)
- Identify blocked claims (ungrounded or unapproved)
- If unresolved blockers → pause and present to user
QUICK_MODE exit: If QUICK_MODE = true, stop here. Present ISSUE_BOARD.md + STRATEGY_PLAN.md to the user and summarize: how many issues per reviewer, shared vs unique concerns, recommended priorities, and evidence gaps. The user can then decide to continue with full rebuttal (/rebuttal — quick mode: false) or write manually.
Phase 3.5: Evidence Sprint (when AUTO_EXPERIMENT = true)
Skip entirely if AUTO_EXPERIMENT is false — instead, pause and present the evidence gaps to the user.
If the strategy plan identifies issues that require new empirical evidence (tagged response_mode: grounded_evidence with evidence_source: needs_experiment):
Generate a mini experiment plan from the reviewer concerns:
- What to run (ablation, baseline comparison, scale-up, condition check)
- Success criterion (what result would satisfy the reviewer)
- Estimated GPU-hours
Invoke /experiment-bridge with the mini plan:
/experiment-bridge "rebuttal/REBUTTAL_EXPERIMENT_PLAN.md"
Wait for results, then update ISSUE_BOARD.md:
- Tag completed experiments as
user_confirmed_result
- Update evidence source for relevant issue cards
If experiments fail or are inconclusive:
- Switch response mode to
narrow_concession or future_work_boundary
- Do NOT fabricate positive results
Save experiment results to rebuttal/REBUTTAL_EXPERIMENTS.md for provenance tracking.
Time guard: If estimated GPU-hours exceed rebuttal deadline, skip and flag for manual handling.
Phase 4: Draft Initial Rebuttal
Create rebuttal/REBUTTAL_DRAFT_v1.md.
Structure:
- Short opener — thank reviewers + 2-4 global resolutions
- Per-reviewer numbered responses — answer → evidence → implication
- Short closing — resolved / remaining / acceptance case
Default reply pattern per issue:
- Sentence 1: direct answer
- Sentence 2-4: grounded evidence
- Last sentence: implication for the paper
Heuristics from 5 successful rebuttals:
- Evidence > assertion
- Global narrative first, per-reviewer detail second
- Concrete numbers for counter-intuitive points
- Name closest prior work + exact delta for novelty disputes
- Concede narrowly when reviewer is right
- For theory: separate core vs technical assumptions
- Answer friendly reviewers too
Hard rules:
- NEVER invent experiments, numbers, derivations, citations, or links
- NEVER promise what user hasn't approved
- If no strong evidence exists, say less not more
Also generate rebuttal/PASTE_READY.txt (plain text, exact character count).
Also generate rebuttal/REVISION_PLAN.md — the overall revision checklist.
This document is the single source of truth for every paper revision promised (explicitly or implicitly) in the rebuttal draft. It exists so the author can track follow-through after the rebuttal is submitted, and so the commitment gate in Phase 5 has a concrete artifact to validate against.
Structure:
Header
- Paper title, venue, character limit, rebuttal round
- Links back to
ISSUE_BOARD.md, STRATEGY_PLAN.md, REBUTTAL_DRAFT_v1.md
Overall checklist — a single flat GitHub-style checklist covering every revision item, so the author can tick items off as they land in the camera-ready / revised PDF:
## Overall Checklist
- [ ] (R1-C2) Add assumption hierarchy table to Section 3.1 — commitment: `approved_for_rebuttal` — owner: author — status: pending
- [ ] (R2-C1) Clarify novelty delta vs. Smith'24 in Section 2 related work — commitment: `already_done` — status: verify wording
- [ ] (R3-C4) Add runtime breakdown figure to Appendix B — commitment: `future_work_only` — status: deferred, note in camera-ready
- ...
Checklist items must be atomic (one paper edit per line) and each must reference its issue_id so it maps back to ISSUE_BOARD.md.
Grouped view — the same items regrouped by (a) paper section/location and (b) severity, so the author can plan the revision pass efficiently.
Commitment summary — counts of already_done / approved_for_rebuttal / future_work_only, plus any needs_user_input items that are blocking.
Out-of-scope log — reviewer concerns that will not trigger a paper revision (e.g. deferred_intentionally, narrow_concession with no edit), with a one-line reason each. This keeps the checklist honest: nothing silently disappears.
Rules for REVISION_PLAN.md:
- Every checklist item must map to at least one
issue_id from ISSUE_BOARD.md.
- Every promise in
REBUTTAL_DRAFT_v1.md that implies a paper edit must appear as a checklist item — if it is not in the plan, it is a commitment-gate violation.
- Never add items that are not backed by the draft or by user-confirmed evidence.
- On rerun / follow-up rounds, update checkbox state in place rather than regenerating from scratch.
Phase 5: Safety Validation
Run all lints:
- Coverage — every issue maps to draft anchor
- Provenance — every factual sentence has source
- Commitment — promises are approved AND every paper-edit promise in the draft appears as a checklist item in
REVISION_PLAN.md (and vice versa — no orphan items in the plan)
- Tone — flag aggressive/submissive/evasive phrases
- Consistency — no contradictions across reviewer replies
- Limit — exact character count, compress if over (redundancy → friendly → opener → wording, never drop critical answers)
Phase 6: Codex Reviewer Stress Test
Resolve this reviewer slot first; the following is the backend=codex example.
spawn_agent:
model: gpt-6-astra
reasoning_effort: xhigh
message: |
Stress-test this rebuttal draft:
[raw reviews + issue board + draft + venue rules]
1. Unanswered or weakly answered concerns?
2. Unsupported factual statements?
3. Risky or unapproved promises?
4. Tone problems?
5. Paragraph most likely to backfire with meta-reviewer?
6. Minimal grounded fixes only. Do NOT invent evidence.
Verdict: safe to submit / needs revision
Save full response to rebuttal/MCP_STRESS_TEST.md. If hard safety blocker → revise before finalizing.
Phase 7: Finalize — Two Versions
Produce two outputs for different purposes:
rebuttal/PASTE_READY.txt — the strict version
- Plain text, exact character count, fits venue limit
- Ready to paste directly into OpenReview / CMT / HotCRP
- No markdown formatting, no extras
rebuttal/REBUTTAL_DRAFT_rich.md — the extended version
- Same structure but with more detail: fuller explanations, additional evidence, optional paragraphs
- Marked with
[OPTIONAL — cut if over limit] for sections that exceed the strict version
- Author can read this to understand the full reasoning, then manually decide what to keep/cut/rewrite
- Useful for follow-up rounds — the extra material is pre-written
Update rebuttal/REBUTTAL_STATE.md
Refresh rebuttal/REVISION_PLAN.md so the overall checklist matches the final draft (add items, mark already_done as checked, carry forward any pending items)
Present to user:
PASTE_READY.txt character count vs venue limit
REBUTTAL_DRAFT_rich.md for review and manual editing
REVISION_PLAN.md checklist — counts of pending / approved / deferred
- Remaining risks + lines needing manual approval
Phase 8: Follow-Up Rounds
When new reviewer comments arrive:
- Append verbatim to
rebuttal/FOLLOWUP_LOG.md
- Link to existing issues or create new ones
- Draft delta reply only (not full rewrite)
- Update
rebuttal/REVISION_PLAN.md in place — add any new checklist items introduced by the follow-up, tick off items the author has already completed, and keep existing items' status current
- Re-run safety lints
- Use Codex MCP reply for continuity if useful
- Rules: escalate technically not rhetorically; concede if reviewer is correct; stop arguing if reviewer is immovable and no new evidence exists
Phase 9: Render HTML view (auto, when RENDER_HTML = true, default)
After Phase 6 (initial rebuttal) or Phase 8 (follow-up rounds) finalize rebuttal/REBUTTAL_DRAFT_rich.md, invoke:
/render-html "rebuttal/REBUTTAL_DRAFT_rich.md"
Full review gate (reviewer-facing pre-submission deliverable). Do NOT render rebuttal/PASTE_READY.txt (it's exact-character-count plain text by design).
Non-blocking: if /render-html fails, log the failure and treat the rebuttal phase as complete — the PASTE_READY.txt and REBUTTAL_DRAFT_rich.md are the canonical outputs.
Skip if RENDER_HTML = false.
Key Rules
- Large file handling: If Write fails, retry with Bash heredoc silently.
- Never fabricate. No invented evidence, numbers, derivations, citations, or links.
- Never overpromise. Only promise what user explicitly approved.
- Full coverage. Every reviewer concern tracked and accounted for.
- Preserve raw records. Reviews and MCP outputs stored verbatim.
- Global + per-reviewer structure. Shared concerns in opener.
- Answer friendly reviewers too. Reinforce supportive framing.
- Meta-reviewer closing. Summarize resolved/remaining/why accept.
- Evidence > rhetoric. Derivations and numbers over prose.
- Concede selectively. Narrow honest concessions > broad denials.
- Don't waste space on unwinnable arguments. Answer once, move on.
- Respect the limit. Character budget is a hard constraint.
- Resume cleanly. Continue from REBUTTAL_STATE.md on rerun.
- Anti-hallucination citations. Any reference added must go through DBLP → CrossRef → [VERIFY].
Review Tracing
After each spawn_agent or send_input reviewer call, save the trace following ../shared-references/review-tracing.md. Write files directly to .aris/traces/rebuttal/<date>_run<NN>/. Respect the --- trace: parameter when present (default: full).
1---2name: rebuttal3description: "Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Use when user says \"rebuttal\", \"reply to reviewers\", \"ICML rebuttal\", \"OpenReview response\", or wants to answer external reviews safely."4argument-hint: "[paper-path-or-review-bundle]"5allowed-tools: Bash(*), Read, Grep, Glob, Write, Edit, Skill, mcp__antigravity__antigravity, mcp__antigravity__antigravity-reply, mcp__grok__grok, mcp__grok__grok-reply, mcp__claude-review__review, mcp__claude-review__review_reply, mcp__claude-review__review_start, mcp__claude-review__review_reply_start, mcp__claude-review__review_status6metadata:7 source: https://skillmd.com/skills/wanshuiyin/rebuttal8---910# Workflow 4: Rebuttal1112> **Before each reviewer slot**, follow [Selectable Reviewers](../shared-references/reviewer-backends.md):13> resolve invocation → `.aris/reviewer.json` → Codex default (fresh native reviewer)14> with `reviewer_route.py` through the canonical helper resolver, preserving this15> slot's tier, fresh contexts, source/image inputs and deterministic gates.16> Codex examples/pins below apply only to `backend=codex`; other routes use their17> own first-call/reply contract. Save the route and actual returned identity;18> unavailable selections are `REVIEW_UNAVAILABLE`. Classify acceptance from actual19> families/completion/scope. Forward invocation reviewer/model/effort overrides20> to reviewer-bearing children. Generation workers are unchanged.212223Prepare and maintain a grounded, venue-compliant rebuttal for: **$ARGUMENTS**2425## Scope2627This skill is optimized for:28- ICML-style **text-only rebuttal**29- strict **character limits**30- **multiple reviewers**31- **follow-up rounds** after the initial rebuttal32- safe drafting with **no fabrication**, **no overpromise**, and **full issue coverage**3334This skill does **not**:35- run new experiments automatically36- generate new theorem claims automatically37- edit or upload a revised PDF38- submit to OpenReview / CMT / HotCRP3940If the user already has new results, derivations, or approved commitments, the skill can incorporate them as **user-confirmed evidence**.4142## Lifecycle Position4344```text45Workflow 1: idea-discovery46Workflow 1.5: experiment-bridge47Workflow 2: auto-review-loop (pre-submission)48Workflow 3: paper-writing49Workflow 4: rebuttal (post-submission external reviews)50```5152## Constants5354- **VENUE = `ICML`** — Default venue. Override if needed.55- **RESPONSE_MODE = `TEXT_ONLY`** — v1 default.56- **REVIEWER_MODEL = `gpt-6-astra`** — Used via Codex MCP for internal stress-testing.57- **REVIEWER_BACKEND = `codex`** — Default: Codex xhigh stress tester. Use `--reviewer: oracle-pro` only when explicitly requested; if Oracle is unavailable, warn and fall back to Codex xhigh. See `../shared-references/reviewer-routing.md`.58- **MAX_INTERNAL_DRAFT_ROUNDS = 2** — draft → lint → revise.59- **MAX_STRESS_TEST_ROUNDS = 1** — One Codex MCP critique round.60- **MAX_FOLLOWUP_ROUNDS = 3** — per reviewer thread.61- **AUTO_EXPERIMENT = false** — When `true`, automatically invoke `/experiment-bridge` to run supplementary experiments when the strategy plan identifies reviewer concerns that require new empirical evidence. When `false` (default), pause and present the evidence gap to the user for manual handling.62- **QUICK_MODE = false** — When `true`, only run Phase 0-3 (parse reviews, atomize concerns, build strategy). Outputs `ISSUE_BOARD.md` + `STRATEGY_PLAN.md` and stops — no drafting, no stress test. Useful for quickly understanding what reviewers want before deciding how to respond.63- **REBUTTAL_DIR = `rebuttal/`**64- **RENDER_HTML = true** — When `true` (default), auto-render `rebuttal/REBUTTAL_DRAFT_rich.md` to HTML after Phase 6 / Phase 8 finalization via `/render-html`. Uses **full review gate** (reviewer-facing pre-submission deliverable). The plain-text `PASTE_READY.txt` is NOT rendered (it's character-counted plain text by design). Set `false` to skip, or pass `— render html: false`. **Non-blocking**: failures don't invalidate the rebuttal.6566> Override: `/rebuttal "paper/" — venue: NeurIPS, character limit: 5000`6768## Required Inputs69701. **Paper source** — PDF, LaTeX directory, or narrative summary712. **Raw reviews** — pasted text, markdown, or PDF with reviewer IDs723. **Venue rules** — venue name, character/word limit, text-only or revised PDF allowed734. **Current stage** — initial rebuttal or follow-up round7475If venue rules or limit are missing, **stop and ask** before drafting.7677## Safety Model7879Three hard gates — if any fails, do NOT finalize:80811. **Provenance gate** — every factual statement maps to: `paper`, `review`, `user_confirmed_result`, `user_confirmed_derivation`, or `future_work`. No source = blocked.822. **Commitment gate** — every promise maps to: `already_done`, `approved_for_rebuttal`, or `future_work_only`. Not approved = blocked.833. **Coverage gate** — every reviewer concern ends in: `answered`, `deferred_intentionally`, or `needs_user_input`. No issue disappears.8485## Workflow8687### Phase 0: Resume or Initialize88891. If `rebuttal/REBUTTAL_STATE.md` exists → resume from recorded phase902. Otherwise → create `rebuttal/`, initialize all output documents913. Load paper, reviews, venue rules, any user-confirmed evidence9293### Phase 1: Validate Inputs and Normalize Reviews94951. Validate venue rules are explicit962. Normalize all reviewer text into `rebuttal/REVIEWS_RAW.md` (verbatim)973. Record metadata in `rebuttal/REBUTTAL_STATE.md`984. If ambiguous, pause and ask99100### Phase 2: Atomize and Classify Reviewer Concerns101102Create `rebuttal/ISSUE_BOARD.md`.103104For each atomic concern:105- `issue_id` (e.g., R1-C2)106- `reviewer`, `round`, `raw_anchor` (short quote)107- `issue_type`: assumptions / theorem_rigor / novelty / empirical_support / baseline_comparison / complexity / practical_significance / clarity / reproducibility / other108- `severity`: critical / major / minor109- `reviewer_stance`: positive / swing / negative / unknown110- `response_mode`: direct_clarification / grounded_evidence / nearest_work_delta / assumption_hierarchy / narrow_concession / future_work_boundary111- `status`: open / answered / deferred / needs_user_input112113### Phase 3: Build Strategy Plan114115Create `rebuttal/STRATEGY_PLAN.md`.1161171. Identify 2-4 **global themes** resolving shared concerns1182. Choose **response mode** per issue1193. Build **character budget** (10-15% opener, 75-80% per-reviewer, 5-10% closing)1204. Identify **blocked claims** (ungrounded or unapproved)1215. If unresolved blockers → pause and present to user122123**QUICK_MODE exit**: If `QUICK_MODE = true`, stop here. Present `ISSUE_BOARD.md` + `STRATEGY_PLAN.md` to the user and summarize: how many issues per reviewer, shared vs unique concerns, recommended priorities, and evidence gaps. The user can then decide to continue with full rebuttal (`/rebuttal — quick mode: false`) or write manually.124125### Phase 3.5: Evidence Sprint (when AUTO_EXPERIMENT = true)126127**Skip entirely if `AUTO_EXPERIMENT` is `false` — instead, pause and present the evidence gaps to the user.**128129If the strategy plan identifies issues that require new empirical evidence (tagged `response_mode: grounded_evidence` with `evidence_source: needs_experiment`):1301311. Generate a mini experiment plan from the reviewer concerns:132 - What to run (ablation, baseline comparison, scale-up, condition check)133 - Success criterion (what result would satisfy the reviewer)134 - Estimated GPU-hours1351362. Invoke `/experiment-bridge` with the mini plan:137 ```138 /experiment-bridge "rebuttal/REBUTTAL_EXPERIMENT_PLAN.md"139 ```1401413. Wait for results, then update `ISSUE_BOARD.md`:142 - Tag completed experiments as `user_confirmed_result`143 - Update evidence source for relevant issue cards1441454. If experiments fail or are inconclusive:146 - Switch response mode to `narrow_concession` or `future_work_boundary`147 - Do NOT fabricate positive results1481495. Save experiment results to `rebuttal/REBUTTAL_EXPERIMENTS.md` for provenance tracking.150151**Time guard**: If estimated GPU-hours exceed rebuttal deadline, skip and flag for manual handling.152153### Phase 4: Draft Initial Rebuttal154155Create `rebuttal/REBUTTAL_DRAFT_v1.md`.156157Structure:1581. **Short opener** — thank reviewers + 2-4 global resolutions1592. **Per-reviewer numbered responses** — answer → evidence → implication1603. **Short closing** — resolved / remaining / acceptance case161162Default reply pattern per issue:163- Sentence 1: direct answer164- Sentence 2-4: grounded evidence165- Last sentence: implication for the paper166167Heuristics from 5 successful rebuttals:168- Evidence > assertion169- Global narrative first, per-reviewer detail second170- Concrete numbers for counter-intuitive points171- Name closest prior work + exact delta for novelty disputes172- Concede narrowly when reviewer is right173- For theory: separate core vs technical assumptions174- Answer friendly reviewers too175176Hard rules:177- NEVER invent experiments, numbers, derivations, citations, or links178- NEVER promise what user hasn't approved179- If no strong evidence exists, say less not more180181Also generate `rebuttal/PASTE_READY.txt` (plain text, exact character count).182183Also generate `rebuttal/REVISION_PLAN.md` — the **overall revision checklist**.184185This document is the single source of truth for every paper revision promised (explicitly or implicitly) in the rebuttal draft. It exists so the author can track follow-through after the rebuttal is submitted, and so the commitment gate in Phase 5 has a concrete artifact to validate against.186187Structure:1881891. **Header**190 - Paper title, venue, character limit, rebuttal round191 - Links back to `ISSUE_BOARD.md`, `STRATEGY_PLAN.md`, `REBUTTAL_DRAFT_v1.md`1921932. **Overall checklist** — a single flat GitHub-style checklist covering **every** revision item, so the author can tick items off as they land in the camera-ready / revised PDF:194195 ```markdown196 ## Overall Checklist197198 - [ ] (R1-C2) Add assumption hierarchy table to Section 3.1 — commitment: `approved_for_rebuttal` — owner: author — status: pending199 - [ ] (R2-C1) Clarify novelty delta vs. Smith'24 in Section 2 related work — commitment: `already_done` — status: verify wording200 - [ ] (R3-C4) Add runtime breakdown figure to Appendix B — commitment: `future_work_only` — status: deferred, note in camera-ready201 - ...202 ```203204 Checklist items must be **atomic** (one paper edit per line) and each must reference its `issue_id` so it maps back to `ISSUE_BOARD.md`.2052063. **Grouped view** — the same items regrouped by (a) paper section/location and (b) severity, so the author can plan the revision pass efficiently.2072084. **Commitment summary** — counts of `already_done` / `approved_for_rebuttal` / `future_work_only`, plus any `needs_user_input` items that are blocking.2092105. **Out-of-scope log** — reviewer concerns that will **not** trigger a paper revision (e.g. `deferred_intentionally`, `narrow_concession` with no edit), with a one-line reason each. This keeps the checklist honest: nothing silently disappears.211212Rules for `REVISION_PLAN.md`:213- Every checklist item must map to at least one `issue_id` from `ISSUE_BOARD.md`.214- Every promise in `REBUTTAL_DRAFT_v1.md` that implies a paper edit must appear as a checklist item — if it is not in the plan, it is a commitment-gate violation.215- Never add items that are not backed by the draft or by user-confirmed evidence.216- On rerun / follow-up rounds, update checkbox state in place rather than regenerating from scratch.217218### Phase 5: Safety Validation219220Run all lints:2211. **Coverage** — every issue maps to draft anchor2222. **Provenance** — every factual sentence has source2233. **Commitment** — promises are approved AND every paper-edit promise in the draft appears as a checklist item in `REVISION_PLAN.md` (and vice versa — no orphan items in the plan)2244. **Tone** — flag aggressive/submissive/evasive phrases2255. **Consistency** — no contradictions across reviewer replies2266. **Limit** — exact character count, compress if over (redundancy → friendly → opener → wording, never drop critical answers)227228### Phase 6: Codex Reviewer Stress Test229230> Resolve this reviewer slot first; the following is the `backend=codex` example.231232```233spawn_agent:234 model: gpt-6-astra235 reasoning_effort: xhigh236 message: |237 Stress-test this rebuttal draft:238 [raw reviews + issue board + draft + venue rules]239240 1. Unanswered or weakly answered concerns?241 2. Unsupported factual statements?242 3. Risky or unapproved promises?243 4. Tone problems?244 5. Paragraph most likely to backfire with meta-reviewer?245 6. Minimal grounded fixes only. Do NOT invent evidence.246247 Verdict: safe to submit / needs revision248```249250Save full response to `rebuttal/MCP_STRESS_TEST.md`. If hard safety blocker → revise before finalizing.251252### Phase 7: Finalize — Two Versions253254Produce **two outputs** for different purposes:2552561. **`rebuttal/PASTE_READY.txt`** — the strict version257 - Plain text, exact character count, fits venue limit258 - Ready to paste directly into OpenReview / CMT / HotCRP259 - No markdown formatting, no extras2602612. **`rebuttal/REBUTTAL_DRAFT_rich.md`** — the extended version262 - Same structure but with **more detail**: fuller explanations, additional evidence, optional paragraphs263 - Marked with `[OPTIONAL — cut if over limit]` for sections that exceed the strict version264 - Author can read this to understand the full reasoning, then manually decide what to keep/cut/rewrite265 - Useful for follow-up rounds — the extra material is pre-written2662673. Update `rebuttal/REBUTTAL_STATE.md`2684. Refresh `rebuttal/REVISION_PLAN.md` so the overall checklist matches the final draft (add items, mark `already_done` as checked, carry forward any `pending` items)2695. Present to user:270 - `PASTE_READY.txt` character count vs venue limit271 - `REBUTTAL_DRAFT_rich.md` for review and manual editing272 - `REVISION_PLAN.md` checklist — counts of pending / approved / deferred273 - Remaining risks + lines needing manual approval274275### Phase 8: Follow-Up Rounds276277When new reviewer comments arrive:2782791. Append verbatim to `rebuttal/FOLLOWUP_LOG.md`2802. Link to existing issues or create new ones2813. Draft **delta reply only** (not full rewrite)2824. Update `rebuttal/REVISION_PLAN.md` in place — add any new checklist items introduced by the follow-up, tick off items the author has already completed, and keep existing items' status current2835. Re-run safety lints2846. Use Codex MCP reply for continuity if useful2857. Rules: escalate technically not rhetorically; concede if reviewer is correct; stop arguing if reviewer is immovable and no new evidence exists286287### Phase 9: Render HTML view (auto, when `RENDER_HTML = true`, default)288289After Phase 6 (initial rebuttal) or Phase 8 (follow-up rounds) finalize `rebuttal/REBUTTAL_DRAFT_rich.md`, invoke:290291```292/render-html "rebuttal/REBUTTAL_DRAFT_rich.md"293```294295Full review gate (reviewer-facing pre-submission deliverable). Do NOT render `rebuttal/PASTE_READY.txt` (it's exact-character-count plain text by design).296297**Non-blocking**: if `/render-html` fails, log the failure and treat the rebuttal phase as complete — the `PASTE_READY.txt` and `REBUTTAL_DRAFT_rich.md` are the canonical outputs.298299Skip if `RENDER_HTML = false`.300301## Key Rules302303- **Large file handling**: If Write fails, retry with Bash heredoc silently.304- **Never fabricate.** No invented evidence, numbers, derivations, citations, or links.305- **Never overpromise.** Only promise what user explicitly approved.306- **Full coverage.** Every reviewer concern tracked and accounted for.307- **Preserve raw records.** Reviews and MCP outputs stored verbatim.308- **Global + per-reviewer structure.** Shared concerns in opener.309- **Answer friendly reviewers too.** Reinforce supportive framing.310- **Meta-reviewer closing.** Summarize resolved/remaining/why accept.311- **Evidence > rhetoric.** Derivations and numbers over prose.312- **Concede selectively.** Narrow honest concessions > broad denials.313- **Don't waste space on unwinnable arguments.** Answer once, move on.314- **Respect the limit.** Character budget is a hard constraint.315- **Resume cleanly.** Continue from REBUTTAL_STATE.md on rerun.316- **Anti-hallucination citations.** Any reference added must go through DBLP → CrossRef → [VERIFY].317318## Review Tracing319320After each `spawn_agent` or `send_input` reviewer call, save the trace following `../shared-references/review-tracing.md`. Write files directly to `.aris/traces/rebuttal/<date>_run<NN>/`. Respect the `--- trace:` parameter when present (default: `full`).