Prose Mechanics

Diagnostic audits for sentence-level prose quality on near-final drafts. Each audit is a focused pass that produces a flagged-issues report; the author reviews and applies fixes before moving to the next audit. Works for fiction or nonfiction.

Session Continuity

Audit work is iterative across multiple sessions. Claude has no memory between them, so the audit tracker is your persistent state.

• At session start: Read audit-tracker.md in the project directory (copy from assets/audit-tracker-template.md if it doesn't exist). Check which audits have run on which chapters and what's still outstanding.
• At session end: Update the tracker with what was audited, what was flagged, and what was resolved. Note the stopping point.
• Surface unresolved questions: If prior audits flagged issues the author hasn't addressed, list them at session start so the user can decide what to take on.

Core Concept

Audits are diagnostics, not edits. Each pass scans for one specific class of failure, produces a list of flagged passages, and stops. The author—not the audit—decides whether each flag is a real problem and how to fix it.

When to Use