bmad-editorial-review-structure

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

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-editorial-review-structure-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-editorial-review-structure
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-editorial-review-structure
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-editorial-review-structure-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for users who previously relied on the standalone structural editorial review, which has been merged into the unified bmad-review skill. It ensures existing workflows and prompts continue to produce the familiar structural review report without breaking changes. ## Core Features & Use Cases - Deprecation Forwarding: Routes all requests to the bmad-review skill using only the structure lens, passing through the same inputs and any also_consider areas. - Legacy Report Format: Outputs the classic report shape with a Document Summary block, numbered Recommendations list (CUT/MERGE/MOVE/CONDENSE/QUESTION/PRESERVE with rationale and word impact), and a closing Summary with estimated reduction. - Use Case: A writer with an existing habit or automation that invokes the structural review on a draft article continues to receive the same recommendations format even though the underlying logic now lives in bmad-review. ## 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.

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 review on my document?

Invoke this skill on your content and it forwards the request to bmad-review with only the structure lens active. You receive numbered recommendations tagged CUT, MERGE, MOVE, CONDENSE, QUESTION, or PRESERVE, each with rationale and word impact.

What happened to the standalone structural review skill?

It has been deprecated and merged into the bmad-review skill. This skill remains as a compatibility shim that forwards your request and renders results in the legacy 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 a Recommendations list and a closing Summary with total recommendations and estimated reduction.

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

The skill outputs exactly the message: No substantive changes recommended. This indicates the document structure passed review without identified cuts, merges, or moves.

Can I pass additional review areas alongside the structure lens?

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