reversa-audit

A requirements audit detects coverage gaps and contradictions by cross-checking requirements.md, roadmap.md, and actions.md. It classifies inconsistencies by severity to prevent wasted engineering effort and ensure forward-cycle coherence.

Run the audit by triggering the reversa-audit command for the active feature. The process validates that requirements.md, roadmap.md, and actions.md exist, cross-checks them, and writes a structured findings report to the feature directory.

The best way to find roadmap and action contradictions is a severity-based cross-document audit. It compares planned milestones against tracked execution actions, classifying coverage gaps and conflicts as CRITICAL, HIGH, MEDIUM, or LOW for targeted human resolution.

No, a consistency check audit does not modify source requirements or roadmap files. The process enforces a read-only safety guarantee on input documents, writing structured findings and pass/fail lists only to a dedicated audit report file.

If required roadmap or actions artifacts are missing during an audit, operational guardrails halt the process. The audit validates that all three required documents exist before proceeding to ensure accurate cross-checking and prevent incomplete reporting.

Yes, you need a state file to audit active feature requirements and actions. The audit process reads active feature state and active requirements data to scope the cross-check correctly before generating the findings report.