reversa-reviewer

You validate reverse-engineered specs by performing cross-unit consistency checks, verifying canonical file structures, and checking traceability matrices to detect contradictions and coverage gaps.

Confidence scoring in reverse engineering reclassifies specification certainty levels using confidence rules, flagging unresolved gaps and generating actionable validation questions for human stakeholders.

Generate stakeholder questions by identifying critical unresolved gaps during spec review and outputting them to a dedicated questions file, filtering by the configured doc level to ask only essential queries.

Yes, you can check cross-unit conflicts by validating global artifacts and performing cross-unit consistency checks across requirements, design, and task components to detect rule contradictions.

The best way to review per-unit artifacts is to verify required canonical files per unit, run internal consistency checks across requirements and design, and validate transversal traceability coverage outputs.

You should avoid automated spec review when your configured doc level is not essential, or when you lack reverse-engineered artifacts and state configurations required to generate confidence reports.