harness-editorial-review-prose

Editorial review for technical documentation identifies comprehension-impeding issues and provides minimal, conflict-free revisions. It corrects phrasing clarity while preserving the existing document structure and skipping code blocks or frontmatter.

Yes, editorial review works with markdown, plain text, and text-heavy XML. It safely skips code blocks, frontmatter, and structural markup so that only prose is evaluated for clarity and comprehension improvements.

To copyedit specs for AI agents without changing formatting, apply a structure-preserving review that outputs a three-column table of original text, revised text, and change rationale. This ensures minimal edits that do not conflict with existing markup.

The best way to review decision notes for clarity is a deduplicated editorial review that consolidates repeated issues into one entry with locations. This avoids noisy edits and uses questions when a definitive fix is uncertain.

You should not use automated prose correction when a definitive fix is not clear, as it uses questions rather than making risky changes. It also does not rewrite text for stylistic preferences, focusing solely on comprehension-impeding issues.