Research Rebuttal

Quick start

1. Decide whether this stays standalone or becomes ./rebuttal/ inside an orchestrated research suite.
2. Route the venue first with references/venue_rule_matrix.md; if dates, limits, or policy details are decision-critical, re-check the official venue source before finalizing.
3. Initialize the rebuttal pack with scripts/init_rebuttal_pack.py unless usable artifacts already exist.
4. Build the review analysis and issue board before drafting prose.
5. Convert major issues into concrete evidence or manuscript tasks, then draft the correct artifact shape and verify limits with scripts/count_limits.sh.

Modes

Standalone mode

• Work from pasted reviews, PDFs, screenshots, or local notes.
• Do not require a suite root.
• If the user asks for project-level sequencing, current-state inspection, or coordination across multiple research stages, invoke research-pipeline-planner first instead of treating rebuttal drafting as the whole task.
• Remain collaboration-friendly: if research-paper-plan, research-review-loop, experiment outputs, or manuscript diffs already exist, use them.