bmad-editorial-review

Forwards legacy editorial review requests to the bmad-review structure and prose lenses.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-editorial-review-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-editorial-review
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-editorial-review
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-editorial-review-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for workflows that still invoke the deprecated bmad-editorial-review command, routing them to the consolidated bmad-review skill without breaking existing overrides. ## Core Features & Use Cases - Deprecation Shim: Redirects all invocations to the bmad-review skill using its structure and prose lenses, with structure running first. - Legacy Override Resolution: Resolves legacy customize.toml fields such as reader_type, style_guide, and review_output_path and forwards them as pre-resolved values to bmad-review. - Legacy Output Shape: Presents findings in the original two-pass table format with purpose/audience read and reduction summary. - Use Case: A team with existing bmad-editorial-review override files upgrades to the unified review workflow without rewriting their customization files or changing how reports look. ## Quick Start Ask the assistant to run an editorial review on your document and it will forward the request to bmad-review with the structure and prose lenses.

Frequently Asked Questions about bmad-editorial-review

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

FAQPage Schema
How do I run an editorial review after bmad-editorial-review was deprecated?

Invoke the bmad-review skill on your content with the structure and prose lenses, running structure first. The deprecated skill forwards automatically, so existing invocations still work without changes.

What happens to my existing bmad-editorial-review override files?

Legacy overrides in _bmad/custom/bmad-editorial-review.toml files still resolve through the shim and are passed to bmad-review as pre-resolved values. New customization should go in bmad-review's own customize.toml.

Can I run only a structure-only or prose-only review?

Yes. If the caller requests a structure-only or prose-only review, the shim passes only that lens to bmad-review instead of both. Otherwise both lenses run with structure first.

Why does an empty override value not change bmad-review behavior?

An empty legacy field means no legacy override exists, so the shim forwards nothing and bmad-review's own default stands. Only fields that resolved to an actual value are passed through.

What output format does the deprecated editorial review produce?

It produces the legacy two-pass findings table with columns Pass, Original Text, Revised Text, and Changes, preceded by the purpose and audience read. When the structure pass ran, a reduction summary appears below the table.