bmad-editorial-review-prose

Identify and fix communication issues in prose with a three-column editorial table.

4|1|Updated Sep 30, 2024
One-click install
npx skills add https://github.com/co-cddo/ndx --skill bmad-editorial-review-prose-co-cddo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-editorial-review-prose
Source: https://github.com/co-cddo/ndx/tree/main/_bmad/core/skills/bmad-editorial-review-prose
Command: npx skills add https://github.com/co-cddo/ndx --skill bmad-editorial-review-prose-co-cddo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clinical copy-editing that identifies and fixes communication issues in prose, ensuring the author's meaning is clear and unambiguous while preserving voice and intent.

Core Features & Use Cases

  • Detects issues that impede comprehension (structure, clarity, jargon, redundancy) and outputs minimal, targeted fixes.
  • Generates a three-column editorial table detailing Original Text, Revised Text, and Changes, after reviewing the text you provide.
  • Respects code blocks and frontmatter, preserves document structure, and flags uncertain changes for review.
  • Use cases include editing reports, policies, emails, product documentation, and academic writing to improve clarity without altering intent.

Quick Start

Provide the text to review and, optionally, a style guide and reader type, and I will return a three-column editorial table with suggested fixes.

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 copy-edit long documents with code blocks and frontmatter without breaking the structure?

To copy-edit structured documents without breaking them, this prose review workflow preserves document structure and explicitly skips code blocks and frontmatter. It processes provided text to identify communication issues while keeping technical formatting intact.

What is the best way to review technical prose for clarity and redundancy?

The best way to review technical prose for clarity and redundancy is a strict step-by-step editorial workflow. It detects issues that impede comprehension and deduplicates problems to ensure the author's meaning remains unambiguous.

Can I check if my product documentation contains jargon that impedes reader comprehension?

You can check product documentation for jargon by providing the text and optionally specifying a reader type. The review identifies jargon, structural issues, and redundancy, returning targeted fixes to improve reader comprehension.

How do I get a clear overview of suggested copy-editing changes for my report?

To get a clear overview of suggested changes, the review returns a three-column editorial table. This table displays Original Text, Revised Text, and a concise explanation for each change, allowing you to easily evaluate suggested fixes.

Does the editorial review process alter the author's original voice and intent?

The editorial review process does not alter the author's original voice and intent. It applies minimal, targeted fixes to improve clarity and flags uncertain changes for your manual review, ensuring meaning is preserved.