reversa-audit

To cross-check project specifications, you can run a read-only audit that compares requirements, roadmap, and actions files to detect contradictions, coverage gaps, and action sanity issues before execution.

A read-only audit for legacy feature specifications is a strict analysis process that identifies inconsistencies across requirements, roadmap, and actions without modifying the original artifacts, generating a severity-ranked report instead.

You can generate a consistency checking report by running an audit command that compares your active feature's requirements, roadmap, and actions, writing traceable findings with CRITICAL or HIGH impact guidance to an audit markdown file.

No, the specification audit process enforces strict read-only behavior and never alters your analyzed artifacts, ensuring humans can safely resolve spec errors from the generated cross-check report without source file corruption.

Yes, you can use this consistency checking method for AI agent workflows in legacy projects to detect spec errors and coverage gaps safely, allowing you to correct the agent workflow before making any actual changes.

The limitation of strict read-only specification auditing is that it only identifies contradictions and coverage gaps across artifacts, requiring humans to manually resolve the reported spec errors rather than automatically fixing them.