bmad-editorial-review-structure

Propose prioritized CUT, MERGE, MOVE, CONDENSE, QUESTION, and PRESERVE actions for markdown or plain-text documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you improve a document’s structure by proposing cuts, reorganization, and simplification while preserving comprehension, so readers can understand the material faster.

Core Features & Use Cases

  • Structural review before copy-editing: focuses on high-impact reordering and trimming prior to wording polish.
  • Purpose- and audience-aware analysis: infers or applies purpose and target audience, then selects an appropriate structure model.
  • Prioritized, actionable recommendations: produces a prioritized list of CUT, MERGE, MOVE, CONDENSE, QUESTION, and PRESERVE items with impact estimates.

Quick Start

Ask a structural editor to run an editorial review of the provided document text and return prioritized structural recommendations for improving clarity and flow.

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 improve document structure and flow before copy-editing?

You can run a structural editorial review to receive prioritized recommendations for CUT, MERGE, MOVE, CONDENSE, and PRESERVE actions with estimated impact levels to improve clarity and flow.

What is the best way to restructure a markdown document for a specific target audience?

Provide the markdown or plain-text content along with optional YAML fields like style_guide, purpose, target_audience, reader_type, and length_target to validate inputs and produce tailored structural recommendations.

How do I identify cut and merge opportunities to reduce document redundancy?

The review outputs a prioritized list of CUT, MERGE, and CONDENSE items with impact estimates, specifically targeting redundancy removal and structural coherence to align with the reader journey.

Can I use this editorial review for plain-text documents without a predefined style guide?

While the style_guide is an optional YAML input, the review validates provided content and applies inferred purpose and audience parameters to output structural actions with halting conditions.

When should I not use a structural editing review for content editing?

If structural coherence, redundancy removal, and reader journey alignment are already optimized, running this structural review provides minimal value compared to direct copy-editing.