bmad-editorial-review

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

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-editorial-review-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-editorial-review
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-editorial-review
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-editorial-review-tuanpa-nhg-eng

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 every invocation to bmad-review using its structure and prose lenses, running structure first so prose builds on structure findings. - Legacy Override Resolution: Resolves legacy customize.toml fields (reader_type, style_guide, review_guidance, output_preferences, and others) and forwards only non-empty values as pre-resolved inputs to bmad-review. - Legacy Output Shape: Presents results in the original two-pass findings table with purpose/audience context and a reduction summary when the structure pass ran. - Use Case: A team with existing bmad-editorial-review override files upgrades to bmad-review; their custom style guide and reader type settings continue to apply without rewriting configuration. ## 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 with the deprecated bmad-editorial-review skill?

Invoke it as before and it forwards the request to bmad-review with the structure and prose lenses, structure first. If you asked for a structure-only or prose-only review, only that lens is passed through.

What is the difference between bmad-editorial-review and bmad-review?

bmad-editorial-review is deprecated and merged into bmad-review. It acts as a shim that invokes bmad-review's structure and prose lenses and renders results in the legacy two-pass findings table format.

Do my old bmad-editorial-review override files still work?

Yes. Overrides in _bmad/custom/bmad-editorial-review.toml and the user variant still resolve and are forwarded to bmad-review as pre-resolved values. Only non-empty fields are forwarded; empty fields fall through to bmad-review defaults.

Where should new customization for editorial reviews go?

New customization belongs in bmad-review's customize.toml, which documents every field. The legacy customize.toml exists only so old overrides keep resolving and is overwritten on every update.

What output format does the legacy editorial review produce?

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