bmad-editorial-review-prose

Review prose in markdown, plain text, and XML for clarity issues.

Updated May 23, 2026
One-click install
npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-editorial-review-prose-diegosanchespereira1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-editorial-review-prose
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-editorial-review-prose
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-editorial-review-prose-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reviews prose for communication issues that impede comprehension, helping writers fix clarity problems without changing the underlying meaning or voice.

Core Features & Use Cases

  • Minimal editorial fixes: Suggests the smallest change needed to resolve ambiguity, grammar issues, or confusing wording.
  • Structured review output: Returns findings in a three-column table with the original text, revised text, and a brief explanation.
  • Context-aware handling: Skips code blocks, frontmatter, and structural markup while reviewing markdown, plain text, or text-heavy XML.
  • Use case: Use it to clean up product copy, documentation, announcements, or any text that needs clearer communication before publication.

Quick Start

Ask this Skill to review the provided prose for clarity issues and return only the recommended edits in a three-column table.

Frequently Asked Questions about bmad-editorial-review-prose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review prose for clarity without changing the original meaning?

To review prose for clarity without altering meaning, you need an editorial process that suggests minimal fixes for ambiguity and grammar. This approach returns structured revisions in a three-column table while preserving the author's original voice and intent.

Can I copyedit markdown documentation without modifying code blocks and frontmatter?

Yes, you can copyedit markdown documentation while skipping code blocks, frontmatter, and structural markup. A context-aware editorial review targets only the prose text, ensuring that technical formatting and configuration sections remain completely untouched.

What is the best way to apply Microsoft Writing Style Guide principles to product copy?

Applying Microsoft Writing Style Guide principles to product copy involves checking text for communication issues that impede comprehension. The review deduplicates findings and outputs only the minimal suggested fixes needed to align the prose with established clarity standards.

Does editorial review work with plain text and text-heavy XML files?

Editorial review works seamlessly with plain text, markdown, and text-heavy XML files. The process identifies comprehension issues across these formats while automatically bypassing structural markup, ensuring that only human-readable prose receives copyediting suggestions.

How do I get structured editorial feedback for documentation before publication?

To get structured editorial feedback before publication, request a review that returns findings in a three-column format containing original text, revised text, and explanations. This structured output provides deduped, minimal edits that clarify confusing wording without extensive manual proofreading.