reversa-quality

To audit requirements for clarity, review the feature's requirements.md to ensure prose is unambiguous, template sections are complete, and glossary terms are consistent. This reduces planning ambiguity and rework by verifying textual clarity before plan conversion.

A requirements quality audit checks Gherkin scenarios for happy paths, sad paths, and relevant edge cases. It ensures scenario coverage aligns with planning goals without drifting into implementation or testing concerns.

You need a forward-cycle Reversa workflow environment with .reversa/state.json and .reversa/active-requirements.json present. The audit locates feature-dir/requirements.md, runs quality hooks, and writes an atomic report to feature-dir/audit/requirements-audit.md.

You should not use a requirements clarity audit for implementation or test coverage verification. It focuses strictly on requirements clarity, completeness, consistency, and alignment with reversa principles for forward-cycle planning workflows.

To verify requirements align with governance principles, audit the requirements.md against the project's reversa principles rules. This principles alignment review checks consistency and completeness to ensure the feature is plan-ready.