docs-rewrite

Technical documentation improvement can be achieved by running an audit-first workflow that captures a baseline quality score, drafts an approved rewrite plan, and rejects edits if the post-rewrite validation score drops.

Rewriting RFCs or ADRs requires an operator-controlled rewrite plan that applies rubric-aligned patterns, such as answer-first H2s and citation capsules, ensuring technical accuracy and structural clarity are preserved.

Auditing technical writing identifies unsourced assertions and finds Tier 1-3 evidence to source, remove, or reframe them as original data, ensuring all claims meet the required documentation quality rubric.

No, rewriting READMEs and architecture docs requires mandatory pre-edit operator approval, ensuring a section-by-section rewrite plan is explicitly accepted before any structural or clarity edits occur.

Yes, documentation rewriting prevents destructive changes by running a read-only audit to capture the baseline state, then validating the rewritten document against that baseline to reject any score regressions.

Use an audit-then-validate workflow for docs review when editing technical documents like CLAUDE.md files or blog posts that need strict clarity, evidence, and structure adjustments without regressing quality.