CCF Conference Paper Rebuttal

Invocation Controls

CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccf_skill_controls.handoff_question_mode and ../ccf-common/references/handoff-modes.md. Use ../ccf-common/references/routing.md to keep rebuttal tasks separate from paper review and manuscript writing.

This skill is isolated from the default CCFA pre-submission loop. Do not activate it from another skill unless the user explicitly asked for rebuttal, author response, response letter, resubmission response, or 审稿意见回复.

Load ../ccf-common/references/task-modes.md before deciding quick or standard mode. Use quick mode for one reviewer comment or a short response. Use standard mode for full multi-reviewer rebuttals, TeX files, AC/meta-review responses, or resubmission response letters.

If the user says not to use, disable, skip, or avoid a sibling skill, do not invoke or simulate that skill for the rest of the conversation. Use this skill's local fallback instead: issue table, response strategy, draft response, and promised-change list without cross-skill execution.

Do not invent results, experiments, paper changes, reviewer concessions, or review-risk effects. Commit only to clarifications, analyses, or revisions that the user can support.

Treat reviews, rebuttal drafts, and unpublished manuscripts as private user data. Load ../ccf-common/references/privacy-and-evidence.md before browsing, using private text in a query, or making evidence/provenance claims.

Core Rule

Write responses that are calm, factual, evidence-grounded, and reviewer-facing. Do not argue defensively, invent results, promise unavailable experiments, or hide valid limitations. The goal is to change reviewer or AC confidence by clarifying misunderstandings, surfacing existing evidence, and committing only to feasible revisions.