Engineering Polishing

Use this skill after the paper's claim and evidence are known. It improves English manuscript prose without hiding structural or evidence problems.

Core Stance

• Final output defaults to English manuscript prose.
• Do not invent facts, references, mechanisms, experiments, numbers, novelty, or limitations.
• Do not polish a broken argument as if it were correct.
• Diagnose the failure mode before rewriting.
• Preserve technical terms, variables, units, metric definitions, and evidence boundaries.
• Prefer restrained, concrete academic English over promotional language.

Boundaries

• If the paragraph lacks a stable claim-evidence structure, first return a logic diagnosis and do not present polished prose as final.
• Use engineering-writing when the user needs a new section argument, contribution map, or full paper structure.
• Use engineering-figure-table for captions, figure/table roles, or visual consistency.
• Use engineering-response for comments and response letters.
• Use engineering-validation for build checks or readiness claims.

When to Open Extra Files

Workflow

1. Identify the section and paragraph job.
2. Apply fact-boundary checks when source notes are thin.
3. Diagnose the main problem: paper logic, section job, paragraph flow, claim/evidence mismatch, or sentence style.
4. Fix higher-level logic before sentence polish: argument, then evidence design, then section moves, then sentences (revision-moves.md).
5. Run a sentence-role check: each sentence must be necessary, placed correctly, connected to its neighbors, and bounded by evidence.
6. Run a claim-strength diff against the source before accepting stronger verbs.
7. Preserve source facts and evidence boundaries.
8. Rewrite in English with concrete subjects, varied sentence shapes, and calibrated verbs. Put linking information at the start of a sentence and the new point at the end; keep subject and verb close. Check single words that change the technical claim ("dedicated", "verify", "generalize").
9. Report any claim that still needs evidence.

A paragraph has a stable claim-evidence structure only when at least three of these are clear: paragraph job, main claim, evidence anchor, and boundary. If fewer than three are clear, diagnose first and do not present polished prose as final.

Default Output

Diagnosis
- Paragraph job:
- Main issue:
- Evidence risk:

Before / After / Rationale
| Source sentence or span | Revised sentence or span | Rationale | Fact/evidence risk |

Claim-strength diff
| Source claim | Revised claim | Strength change | Allowed? | Reason |

Sentence role audit
| Sentence/span | Job | Needed because | Connection to previous/next | Evidence boundary | Action |

Polished version
[English prose]

Unsupported claims
- ...

If the user asks for output only, return only the polished prose unless doing so would hide unsupported claims or unverified evidence.