reversa-audit

To audit requirements and roadmap documents for contradictions, run a strict cross-check that compares requirements.md, roadmap.md, and actions.md to detect coverage gaps and conflicting decisions before implementation proceeds.

A cross-check audit for engineering planning validates that every requirement and scenario is reflected by roadmap decisions and actions, while also checking terminology consistency, missing referenced IDs, and legacy domain rule coherence.

You validate coverage gaps and identifier consistency by performing a read-only audit that flags inconsistent terms, missing referenced IDs, and verifies that referenced external and interface contracts actually exist.

Yes, you can generate a severity-ranked audit report for feature governance that categorizes findings into CRITICAL, HIGH, MEDIUM, and LOW levels, writing the cross-check markdown directly to the feature directory.

No, the requirements and roadmap consistency audit enforces read-only behavior, meaning it produces a severity-ranked finding report without changing any of the original requirements, roadmap, or actions documents.