reversa-quality

Auditing requirements writing quality involves evaluating the feature's requirements.md file for clarity, completeness, and consistency. The process produces a formatted audit file detailing issues and suggested improvements, indicating whether requirements are approved, need clarifications, or require rework.

A requirements consistency audit checks the textual coherence and completeness of your requirements.md file against project principles. You need to run it when a feature's requirements are ready for review, ensuring reliable planning and avoiding rework before implementation begins.

Checking requirements.md clarity and completeness standards requires applying a forward-quality process across the document. This generates a structured audit report with categories for clarity, completeness, consistency, and alignment, returning a rewritten formatted audit file for your feature directory.

Yes, you can generate a structured review report for feature requirements without external dependencies. The skill operates independently, referencing the project's .reversa state and templates to evaluate text quality and output an audit file at feature-dir/audit/requirements-audit.md.

The best way to format a requirements review is to apply a standard forward-quality process that outputs a rewritten audit file. This structured report explicitly indicates whether the requirements are approved, require clarifications, or need rework, streamlining the planning phase.

Requirements reviews fail to catch inconsistencies when they lack a structured audit process evaluating alignment with principles. Applying a standardized quality audit to requirements.md identifies coherence and clarity issues early, producing a detailed report to prevent implementation rework.