| name | rewrite-abstract-intro |
| description | Restructure and iteratively rewrite a systems paper's abstract and introduction from their current state while preserving claims, evidence, citations, numbers, notation, and established terminology. Use when the user asks to rewrite, reorganize, rebuild, or fix the abstract or introduction, when their logic or paragraph roles are wrong, or after major claim/result changes invalidate the opening. Use rewrite-paper-section for body sections and iter-refine-writing for whole-paper polish. |
Rewrite Abstract And Introduction
Rebuild the paper opening from the current paper. Preserve technical meaning and evidence. Move before rewriting, rewrite before inventing, and never invent a claim, number, mechanism, citation, or insight.
Do not perform any Git operation. Return the rewritten paper to the caller.
Required References
Read both completely before editing:
references/abstract-intro-revision.md — the complete workflow, source-of-truth rules, planning step, paragraph-by-paragraph process, constraints, self-check, and output contract.references/abstract-intro-structure.md — sentence-level abstract roles, introduction paragraph roles, optional-paragraph conditions, correspondence rules, and causal logic requirements.
For a two-page extended abstract, also read check-paper-structure-flow's references/extended-abstract-2p.md and use its format instead of forcing a separate Introduction or contribution list. Preserve the same source-fidelity, no-invention, citation, number, and logic constraints.
Execution
Follow both references in full. Use the complete paper body as the source of truth for claims and numbers. Obtain confirmation for the reorganization plan on a standalone request; when invoked inside iter-refine-writing, write the plan to the round log and continue.
Compile and perform the abstract-to-introduction correspondence and end-to-end logic checks before returning. Hand body-section work to rewrite-paper-section and whole-paper polish to iter-refine-writing.
