cleanup-and-review-docs

To clean up AI-generated documentation, apply an editorial review process that removes duplication, normalizes formatting, and aligns terminology without altering factual content. This refines text for clarity and consistency, ensuring final delivery quality.

The best way to remove placeholders from technical docs is using a targeted cleanup process that eliminates leftover markers like "[TBD]". Unresolved items are either resolved or clearly flagged for follow-up to ensure the documentation is delivery-ready.

Yes, you can review and fix editorial consistency in a specific docs directory. The cleanup process applies directly to the `{scope}/docs/` directory, aligning terminology and fixing minor cross-link issues to ensure uniform formatting across all files.

Yes, you need validated files, validation findings, and quality checklists before starting the editorial cleanup. These inputs guide the refinement process to ensure the review addresses actual issues without inventing new facts or altering technical content.

An editorial cleanup process for AI-generated content is limited to refining consistency, readability, and formatting without inventing new facts. It does not generate new documentation or validate technical accuracy, serving strictly to polish existing validated files for final delivery.