reversa-reviewer

Specification consistency review checks per-unit requirements, design, and tasks documents to detect internal contradictions and coverage gaps that could block reimplementation. It validates reverse-engineered specs by finding inconsistencies and surfacing targeted questions for ambiguous items.

Confidence rules classify reverse engineering assertions into three levels: confirmed, inferred, and gaps. Confidence reclassification re-evaluates every statement in requirements.md, design.md, and tasks.md to ensure all claims follow the proper confidence-rules.md classifications.

Generate validation questions for missing specification requirements by identifying unresolved gap items during the review phase. The process produces structured questions for these unresolved items, optionally supporting cross-review when the review mode requires it, so humans can confirm anything ambiguous or missing.

You can review reverse-engineered specs without a dedicated traceability matrix by checking per-unit requirements, design, and tasks files for coverage gaps directly. The review process validates traceability by ensuring design and tasks fully cover the specified requirements without needing a separate matrix file.

The Reversa reviewer operates across unit folders containing requirements.md, design.md, and tasks.md plus optional specification artifacts. While it reviews available files, missing tasks.md may limit coverage gap detection and block full reimplementation validation, reducing the overall confidence report accuracy.

Avoid automated spec validation when your reverse-engineered specifications lack the required unit folder structure with requirements.md, design.md, and tasks.md files. The review process depends on these artifacts to detect coverage gaps and reclassify confidence levels accurately across the specification set.