reversa-audit

A documentation consistency audit compares requirements, roadmap, and actions files to identify coverage gaps, terminology mismatches, missing identifiers, and unsafe action dependencies. This cross-checking process ensures every requirement and scenario is represented in decisions and actions.

Documentation drift in forward-cycle planning occurs when requirements, roadmap, and actions artifacts become mismatched or incomplete over time. It is caused by coverage gaps, terminology mismatches, missing identifiers, and legacy rule conflicts that lead to misimplementation of active features.

Generating a severity-ranked report for requirements traceability involves cross-checking active feature artifacts and labeling findings as CRITICAL, HIGH, MEDIUM, or LOW. The report assigns stable finding IDs to help humans prioritize fixes for documentation inconsistencies and missing coverage.

Read-only documentation auditing guarantees no modification of the analyzed requirements, roadmap, and actions artifacts. It verifies artifact existence and active requirements state, writing audit results only to the designated output file at feature-dir/audit/cross-check.md without altering source documents.

You should run a cross-check audit on active feature documentation during forward-cycle planning workflows whenever documentation drift might cause misimplementation. It is needed when verifying that each requirement and scenario is represented in downstream decisions and actions before proceeding with development.

Detecting legacy rule conflicts and unsafe action dependencies across feature docs requires cross-checking requirements, roadmap, and actions artifacts. The audit identifies these inconsistencies alongside coverage gaps and terminology mismatches, generating a severity-ranked report with stable finding IDs for resolution.