bmad-editorial-review-prose

To copyedit markdown documentation without altering meaning, you can review prose for clarity, flow, and terminology consistency while preserving structural markup and skipping code blocks. This process flags awkward phrasing and suggests minimal revisions.

Yes, you can review text-heavy XML for grammar and clarity issues. The editorial review process skips structural markup and frontmatter, focusing strictly on the prose to flag communication problems and suggest minimal revisions that preserve the underlying structure.

The best way to enforce a style guide on AI-generated text is to apply a disciplined editorial review that flags inconsistent terminology and awkward phrasing. This process generates minimal revision suggestions that honor the provided style guide constraints.

Yes, prose review preserves code blocks and frontmatter in plain text files. The process specifically skips structural markup, frontmatter, and code blocks, dedicating analysis exclusively to the surrounding prose to ensure technical formatting remains completely untouched.

You fix unclear references and inconsistent terminology in product writing by running an editorial review that identifies these specific communication issues. It returns a three-column table showing the original text, revised text, and a short explanation for each fix.

A limitation of automated prose review is that it focuses strictly on communication issues impeding comprehension, meaning it will not restructure your document or alter the underlying meaning, and it skips code blocks and frontmatter entirely during analysis.