bmad-editorial-review-structure

Evaluate document hierarchy against Pyramid or Tutorial structures for clarity.

Updated May 13, 2026
One-click install
npx skills add https://github.com/Markuson/ivo_corr --skill bmad-editorial-review-structure-markuson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-editorial-review-structure
Source: https://github.com/Markuson/ivo_corr/tree/main/.agents/skills/bmad-editorial-review-structure
Command: npx skills add https://github.com/Markuson/ivo_corr --skill bmad-editorial-review-structure-markuson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses structural bloat and poor information flow in professional documents, ensuring that content is concise, logical, and optimized for the reader's attention.

Core Features & Use Cases

  • Structural Analysis: Evaluates document hierarchy against proven models like Pyramid or Tutorial structures.
  • Editorial Recommendations: Provides actionable feedback on cutting, merging, or reordering content to improve clarity.
  • Use Case: Use this when you have a draft of a technical guide or project proposal that feels disorganized or overly wordy and you need a professional structural critique before final copy editing.

Quick Start

Run the bmad-editorial-review-structure skill on the provided document content to receive a prioritized list of structural improvements.

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 the structural clarity and information density of technical documentation?

To improve structural clarity and information density, perform a structural editorial review that evaluates document hierarchy against proven models like Pyramid structures to ensure optimal reader comprehension.

When do I need a structural editorial review for a project proposal?

You need a structural editorial review for a project proposal when your draft feels disorganized or overly wordy and requires logical reorganization or length reduction before final copy editing.

What is the best way to reduce document bloat in instructional guides?

The best way to reduce document bloat in instructional guides is to evaluate content against specific structural models and reader-type principles, applying actionable feedback on cutting, merging, or reordering content.

Can I use this to reorganize information flow in technical drafts?

Yes, you can use this to reorganize information flow in technical drafts by evaluating document hierarchy and providing prioritized structural recommendations to enhance logical flow and optimize reader attention.

Does this editorial review focus on structural changes or copy editing?

This editorial review focuses on structural changes, providing actionable feedback on logical reorganization and length reduction to resolve structural bloat, rather than focusing on final copy editing.

Why does my technical guide feel disorganized despite having good content?

Your technical guide feels disorganized because of poor information flow and structural bloat, which can be resolved by evaluating document hierarchy against proven models like Tutorial structures to ensure logical organization.