reversa-audit

Cross-check reporting compares requirements.md, roadmap.md, and actions.md to identify inconsistencies, coverage gaps, and terminology mismatches across feature-level documentation. It generates a non-destructive report classifying findings by severity to help teams verify alignment and traceability.

Traceability gaps between requirements and actions occur when functional requirements lack corresponding roadmap decisions or action items. A cross-check audit identifies these missing links and reports them as coverage gaps, suggesting corrective steps to restore alignment.

Yes, you can cross-check feature documentation without modifying the original markdown files because the auditor operates in strict read-only mode. It writes findings exclusively to a separate cross-check.md report file, ensuring analyzed artifacts remain unaltered.

The best way to verify alignment across product lifecycle documentation is to perform a cross-check audit that traces every functional requirement to a roadmap decision and an action. This classifies inconsistencies by severity and generates actionable corrective guidance.

Limitations to cross-checking terminology mismatches include focusing strictly on requirements.md, roadmap.md, and actions.md, meaning files outside this core trio are not analyzed. The auditor also stops at suggesting human corrective steps rather than automatically fixing mismatches.