bmad-editorial-review-structure

To improve document clarity without altering meaning, apply a structural editorial review that proposes targeted cuts, reorganization, and simplification. This process identifies redundancies and scope gaps to tighten the narrative while preserving the original intent.

The best way to edit long technical documents is using a stepwise, repeatable editorial workflow that runs before copy editing. It applies deterministic recommendations like CUT, MERGE, MOVE, and CONDENSE to optimize structure and logical flow.

Yes, you can use a structural review to fix coherence issues in API documentation. The workflow analyzes technical documents and structured content to identify inefficiencies and propose concise edits that maintain logical flow.

Identify structural inefficiencies in a research report through deep structural analysis that evaluates the document for redundancies and scope gaps. This analysis provides explicit recommendations to reorganize and condense content for clarity.

Yes, structural editing happens before copy editing. Running a stepwise editorial workflow first ensures that major structural reorganization, merging, and condensing are complete before focusing on sentence-level copy edits.