/gaia-editorial-prose performs a clinical copy-editing review on a document, flagging ambiguity, inconsistency, redundancy, jargon, passive voice, sentence complexity, and tone shifts. Every finding includes a specific line reference, severity (critical, major, minor, style), and a concrete suggested fix.
When to use it
You finished writing a document and want a thorough prose review.
A document feels unclear and you want specific improvement suggestions.
Prerequisites
A target document must exist. If not provided, the command asks.
Load document Reads the target and identifies its type (PRD, architecture, story, etc.) to calibrate jargon expectations.
Analyze prose Scans across seven dimensions: ambiguity, inconsistency, redundancy, jargon, passive voice, sentence complexity, and tone shifts.
Generate report Produces a findings table with executive summary and an overall readability score (Clear, Mostly Clear, Needs Work, Major Issues).
Inputs
Input
Source
Description
target-doc-path
Command argument
Path to the document to review.
Outputs
Output
Location
Description
Findings report
Console output (display-only by default)
Per-finding severity, location, issue, and suggested fix. Save to disk on explicit request.
Example session
> /gaia-editorial-prose .gaia/artifacts/planning-artifacts/prd.md
## Executive Summary
Mostly Clear. Two inconsistencies in terminology and several long sentences.
| Severity | Location | Issue | Suggested Fix |
|----------|----------|-------|---------------|
| major | S3, line 42 | "the system" vs "the platform" used interchangeably | Pick one term and use it consistently |
| minor | S5, line 89 | 52-word sentence with 3 nested clauses | Split into two sentences |
| style | S2, line 15 | Passive: "is handled by the middleware" | Active: "the middleware handles" |
Overall readability: Mostly Clear
What to run next
Apply the suggested fixes and re-run to verify improvement.