CCF Paper Writer

Invocation Controls

CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccf_skill_controls.handoff_question_mode, ../ccf-common/references/handoff-modes.md, and ../ccf-common/references/task-modes.md.

This is the manuscript text owner. It also owns local compression and presentation adaptation because both change paper wording or paper-derived communication. Keep idea scope, method mechanism, experiments, numbers, and conclusions unchanged unless the user explicitly authorizes a research-scope change. Follow ../ccf-common/references/task-modes.md, especially the output-flexibility rule: user-requested output format comes before this skill's internal checklist shape.

Run ccf-humanization as the first manuscript-facing preflight and apply ../ccf-humanization/references/humanization-policy.md. Write direct academic prose without defensive strategies, reviewer simulation, boilerplate disclaimers, repeated improbable cases, or internal engineering-status narration. Put concerns that require judgment in a separate user-review warning; do not inject warning prose or edit files solely to encode a warning. Verify internally that every method named in the paper is a confirmed full version under ../ccf-humanization/references/experiment-discipline.md; never substitute a simplified, toy, proxy, reduced, approximate, or debug version. In the manuscript, state the actual method and scientifically relevant configuration naturally; do not write that it is confirmed, approved, or publication-ready.

Do not invent results, baselines, experiments, reviewer impact, or missing evidence. For citations, never guess bib entries: search for the correct paper and obtain its bib entry before citing references/citation-workflow.md. Handle unsupported claims through a narrower accurate claim or a separate user-review warning; do not insert defensive caveats into the manuscript without approval.

When running local writing self-review, score-risk checks, or reviewer-style revision loops, load ../ccf-common/references/review-output-standards.md. Use scores as diagnostic feedback only; do not present them as acceptance probabilities.

Core Rule

Write for the target CCF venue, not for a generic paper. Improve structure, section logic, paragraph roles, contribution framing, claim-evidence alignment, reviewer-facing clarity, and concise presentation. A submission manuscript should also target the venue's usable page budget: too short is a writing failure, not just a harmless demo choice; too long triggers compression. Do not use reference papers to copy wording, claims, examples, technical content, or distinctive phrasing.

The visible output should feel like useful writing, not a process report. Use planning tables and checklists internally; show them only when the user asks for planning, audit status, or rationale.