Writing Audit

Audit and diagnosis of an existing piece of writing — at the line, the mechanics, and the structure. Provenance lives in skill.json; this file is runtime routing only.

Produces: an intent-specific scored report — revision-report.md (revise), copyedit-report.md (copyedit), or diagnosis-report.md (diagnose) — with severity-rated findings, concrete fixes, and the reader the finding costs.

Boundaries

Do NOT use to write or structure something NEW (use writing-design), to audit a documentation system's IA, retrieval, or telemetry (use docs-audit), or to review product UI copy as a usability surface (use ux-audit).

Core principle

Name the reader's cost, not your taste. Every finding ties to a concrete reader and a concrete cost ("a scanner can't find the ask"), carries a severity, and proposes a fix. A change that only reflects preference is a 0 — say so.