reversa-quality

To audit requirements, analyze the textual quality of your requirements.md to identify ambiguities, gaps, and clarity issues across categories like completeness, consistency, and edge cases, generating a structured quality report with remediation suggestions.

A requirements quality audit is a rigorous review of your requirements.md prose to ensure it is comprehensible and unambiguous. You need it before planning or implementation to prevent rework caused by misaligned project principles.

Yes, you can check edge cases and alignment by applying the audit across categories such as clarity, completeness, consistency, edge cases, and alignment with project principles using defined templates and workflow.

Generate a structured report for requirement ambiguities by auditing the active feature's requirements.md and producing a quality report in the repository feature directory under audit requirements, complete with a verdict and remediation suggestions.

The best way to prevent rework from unclear requirement documentation is to perform a rigorous audit of your requirements.md, identifying clarity issues and gaps to ensure comprehensible prose before implementation begins.