reversa-audit

To cross-check requirements, roadmap, and actions documents for feature alignment, run an audit that compares the three artifacts and generates a report highlighting inconsistencies by severity. The process requires core artifacts to exist and reads state files to determine output folders.

A forward audit for feature consistency is an optional workflow step that identifies inconsistencies among requirements.md, roadmap.md, and actions.md. It reports misalignments categorized by severity levels like CRITICAL, HIGH, MEDIUM, and LOW.

Yes, running a document consistency audit requires reading .reversa/state.json and .reversa/active-requirements.json to determine output folders. The audit also enforces that core artifacts like requirements.md, roadmap.md, and actions.md exist before processing.

A feature audit report shows CRITICAL inconsistencies because the cross-check process evaluates requirements, roadmap, and actions documents, classifying severe misalignments under CRITICAL, HIGH, MEDIUM, or LOW severity to help prioritize corrections.

No, the cross-check audit operates under a strict read-only policy and will never modify the analyzed artifacts. It only reads requirements.md, roadmap.md, and actions.md to generate a human-ready report of inconsistencies.