bmad-editorial-review-structure

Forwards structural editorial review requests to the bmad-review skill with legacy report formatting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for users who previously relied on a dedicated structural editorial review, by forwarding requests to the consolidated bmad-review skill while keeping the familiar legacy report format. ## Core Features & Use Cases - Deprecation Forwarding: Redirects all structural review requests to the bmad-review skill using only the structure lens. - Legacy Report Shape: Produces the classic output format with a Document Summary block, numbered CUT/MERGE/MOVE/CONDENSE/QUESTION/PRESERVE recommendations, and a closing Summary. - Use Case: A writer with an existing workflow that invokes the old structural review on a draft article can keep the same command and receive the same style of structural recommendations, including estimated word-count reduction. ## Quick Start Ask the assistant to run a structural editorial review on your document and it will forward the request to bmad-review with the structure lens and return the legacy report.

Frequently Asked Questions about bmad-editorial-review-structure

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

FAQPage Schema
How do I run a structural editorial review on my document?

Invoke this skill on your content and it forwards the request to the bmad-review skill using only the structure lens. You receive the legacy report with a Document Summary, numbered recommendations, and a closing Summary.

What happened to the standalone structural review skill?

It was merged into the bmad-review skill and is now deprecated. This skill exists only as a forwarding shim that preserves the old invocation pattern and report format.

What output format does the structural review produce?

It produces a Document Summary block covering purpose, audience, reader type, structure model, and length, followed by numbered CUT/MERGE/MOVE/CONDENSE/QUESTION/PRESERVE recommendations with rationale and word impact, plus a closing Summary.

What happens if no structural issues are found in my document?

The skill outputs exactly the phrase: No substantive changes recommended. No report sections or recommendation lists are generated in that case.

Can I pass additional review areas alongside the structure lens?

Yes, any also_consider areas you provide are passed through to the bmad-review skill unchanged. The structure lens remains the primary focus of the forwarded review.