bmad-editorial-review-prose

To review markdown prose for clarity, provide the text to the editorial review tool. It identifies ambiguity, redundancy, and jargon while preserving frontmatter and skipping code blocks, outputting fixes in a structured table.

Yes, you can copy-edit technical documentation while preserving the author voice. The review process maintains the original tone unless a specific change directly improves clarity or resolves structural communication issues.

The best way to identify jargon and redundancy in plain text reports is using a structured stepwise critique. It highlights communication issues without altering content meaning, outputting recommended fixes by location in a three-column table.

Yes, the prose review process works with content containing frontmatter. It supports Markdown, plain text, and frontmatter formats, scanning the text while skipping code blocks to focus purely on editorial improvements.

Automated copy-editing for technical reports focuses on readability without changing technical conclusions. It is limited to identifying ambiguity, redundancy, and structure issues, providing recommendations rather than directly rewriting the original content.

To get a structured critique of communication issues, submit your prose for editorial review. It generates a stepwise set of recommendations formatted as a three-column table detailing the issue, its location, and the suggested fix.