reversa-quality

To audit feature requirements for clarity before planning, you can use a requirements audit tool that reads your active requirements.md file, evaluates it against a quality template, and generates a report with category-scoped findings and a pass/fail verdict.

A requirements quality audit evaluates the textual clarity, consistency, and completeness of written feature requirements. You need one before converting requirements into a plan and code to prevent ambiguity and avoid downstream rework.

To check Gherkin scenario coverage, an audit tool evaluates your requirements document against category-based criteria including scenario coverage, edge cases, and consistency, then outputs a report listing any missing coverage items.

No, the requirements audit does not modify the original requirements.md file. It reads the active feature requirements, analyzes them against a quality template, and atomically persists the findings into a separate requirements-audit.md report.

A requirements consistency check evaluates clarity, consistency, scenario coverage, edge cases, jargon avoidance, and principle alignment. It produces a report containing 10 to 30 category-scoped items with a final pass or fail verdict.

Yes, you can use a requirements audit for forward-cycle quality checks by reading the active feature directory and evaluating the requirements.md file against a quality template to determine planning readiness before development begins.