editorial-review

# Editorial Review (structural pass) Critique and tighten a long deliverable's **argument architecture** — then hand the prose off to the humanization layer. This skill operates on structure only; it never rewrites sentences and never challenges the ideas. The full method (document arcs, operation vocabulary, defect checklist, the hard boundary with `humanization.md`) lives in `reference/editorial-review.md`. Load it; do not restate it here. --- ## Phase 0: Load context 1. Read `reference/editorial-review.md` (the document-model arcs, the operation vocabulary, the defect checklist, the boundary table). 2. Read `.claude/rules/humanization.md` — confirm the boundary: this skill stops at the paragraph; everything below it (rhythm, specificity, banned vocabulary, the calibration gate) belongs to that rule. 3. Read the target document **in full** (the `file:<path>` argument, or the pasted text). Never review a draft you have only skimmed. ## Phase 1: Structural pass 1. **Select one document model** from `reference/editorial-review.md` (proposal arc, intel-brief arc, investor-narrative arc, argument/decision-note arc, or a generic model). State the choice and its primary rule in one sentence: "This deliverable should follow the {model}; its primary rule is {rule}." 2. **Map the structure** — list each major section with an approximate word count. This forces measurement before recommendation. 3. **Walk the defect checklist** (orphan section, claim-without-evidence, evidence-...