Abstract Writing
Write the abstract so that a reader can understand the paper's central problem, answer, evidence, and demonstrated scope without seeing the rest of the manuscript. Do not give every section or contribution equal space.
Read The Evidence First
- Read the current abstract and the title.
- Read the introduction, headline results, conclusion, and limitations when they are available. Inspect the decisive figure, theorem, or experiment behind each abstract claim.
- Treat the manuscript and any example corpus selected for the task as voice evidence. Never infer a result, comparison, number, or limitation from a generic abstract pattern.
- When matching the Simchowitz-group research voice, read example-abstract-patterns.md.
- When no stronger voice sample governs the task, read the sibling academic-voice skill.
If only notes are available, distinguish planned work from completed work. Ask for a missing result when the abstract would otherwise imply evidence that the notes do not contain.
Build One Inferential Arc
Before drafting, state these elements in plain language:
- the concrete problem or successful practice;
- the limitation, tension, or missing explanation;
- the paper's central answer;
- the strongest evidence for that answer;
- the conditions or limitations that determine its scope; and
- the change in understanding or design that follows.
Use only the elements needed to understand the argument. Merge adjacent moves when they express one relation. Reorder them when a result-led opening gives the reader a clearer path. Do not force a separate limitation sentence when the comparator, regime, assumptions, or validation setting already makes the scope clear.
Draft For Understanding
- Establish the tension before naming a method whose purpose would otherwise be unclear.
- Explain the conceptual move before listing algorithmic components.
- Give the headline result enough context to interpret the comparison, guarantee, or mechanism.
- Prefer one decisive comparison to a catalog of benchmarks, settings, and implementation details.
- Separate direct evidence from a proposed explanation. Use "shows" or "demonstrates" for direct evidence, "supports" for partial evidence, and "suggests" or "is consistent with" for interpretation.
- End on the supported implication, design consequence, or limitation that changes the reader's understanding. Do not end by announcing code, future work, or another contribution unless that information matters to the venue.
- Read the final two sentences together. The last sentence should complete the abstract's inferential arc rather than repeat the previous claim at a higher level of abstraction. If the penultimate sentence already provides the natural ending, stop there.
- Do not force uplift or finality. An earned limitation, unresolved question, or precise statement of scope can close an abstract more naturally than a generic implication.
Avoid wrappers such as "This paper presents," "On the empirical side," "On the theoretical side," and "Beyond proposing." They describe the document's inventory instead of explaining the argument. Do not force the draft into a fixed number of sentences or equal-length contribution blocks.
Protect The Claim Boundary
Check every sentence against the manuscript:
- Does the abstract name the same comparator, regime, metric, and uncertainty as the supporting result?
- Does a mechanism claim remain a hypothesis when the evidence is correlational or indirect?
- Does the scope include the conditions needed to interpret the result?
- Do limitations qualify the exact claim they constrain?
- Does the abstract omit interesting details that do not help a reader understand the central answer?
Use literal verbs for claims, evidence, and sections. A claim may hold, apply, depend on an assumption, or have limitations; it does not "stop," "want," or "do the work."
Revise The Cadence
Let sentence length follow the argument. A long sentence can hold a claim and its essential condition when the relation stays clear. A short sentence should carry real emphasis, not manufacture urgency. Avoid repeated sentence openings, contribution announcements, and several consecutive sentences with the same clause structure.
After the claim audit, run the complete sibling general-writing workflow once. It applies Humanizer and the shared cadence pass. Recheck every comparison, qualifier, number, citation, and claim boundary after the prose edit.
Return To The Abstract After The Body Is Final
For an abstract attached to a longer work, revisit it after the title, body, headline results, conclusion, and limitations are stable.
- Compare every abstract sentence with the final work.
- Confirm that the abstract represents the main points as one inferential arc, not as a tour of sections.
- Remove claims that are no longer central, and add any central supported result or limitation that the final revision made necessary.
- Rework the last sentence if the final body changes the implication, scope, or most natural point of closure.
For an abstract-only task, use the final evidence and notes as the completed body, then perform the same check.
Final Abstract Audit
- Can a reader state the problem and central answer after one reading?
- Does the abstract explain why the intervention or analysis resolves the stated tension?
- Is the strongest evidence visible without a benchmark inventory?
- Does each method detail help interpret a result?
- Does the ending state a supported consequence or boundary rather than recap the paper?
- Would deleting the final sentence make the abstract stronger? If so, cut it or replace it with the consequence, boundary, or unresolved point that the preceding evidence actually supports.
- Does the paragraph sound continuous when read at speaking pace?
