bmad-editorial-review-prose

Identifies clarity issues in prose and outputs Original Text, Revised Text, Changes table.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-editorial-review-prose-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-editorial-review-prose
Source: https://github.com/Wizarck/iguanatrader/tree/main/skills/bmad-editorial-review-prose
Command: npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-editorial-review-prose-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clinical copy-editor that reviews text for communication issues and outputs fixes in an explicit three-column table.

Core Features & Use Cases

  • Identifies clarity issues and ambiguous phrasing without rewriting stylistic choices.
  • Outputs a three-column table with Original Text, Revised Text, and Changes, preserving structure.
  • Useful for proofreading, technical documentation, or any prose requiring precise communication.
  • Use Case: A user submits a paragraph with unclear sentences and asks for a precise, minimal fix list.

Quick Start

Provide the text you want reviewed in the content field and optionally specify a style_guide and reader_type to tailor the edits.

Frequently Asked Questions about bmad-editorial-review-prose

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

FAQPage Schema
Can I customize the copy-editing process for a specific style guide and reader type?

Yes, you can customize the copy-editing process by specifying a style_guide and reader_type when submitting your text. This tailors the minimal, defensible fixes to match your exact editorial standards and target audience.

How do I copy-edit text for clarity while preserving the author's original voice?

To copy-edit text for clarity while preserving the author's voice, identify communication issues and apply minimal, defensible fixes rather than full rewrites. This ensures the original stylistic choices remain intact while resolving ambiguous phrasing.

What is the best way to review technical documentation for communication issues?

The best way to review technical documentation for communication issues is using a fixed editorial review sequence that skips code blocks, frontmatter, and structural markup. This targets prose clarity directly while leaving technical syntax untouched.

How do I format prose revisions to clearly show what changed?

Format prose revisions using a structured three-column table containing Original Text, Revised Text, and Changes. This outputs a precise, minimal fix list that transparently documents every defensible edit made to the passage.

Does this editorial review process work on long documents and short passages?

Yes, the editorial review process works on both short passages and longer documents across formal and technical writing. It enforces a fixed review sequence to consistently identify clarity issues regardless of text length.

Can I customize the copy-editing process for a specific style guide and reader type?

Yes, you can customize the copy-editing process by specifying a style_guide and reader_type when submitting your text. This tailors the minimal, defensible fixes to match your exact editorial standards and target audience.