reversa-quality

A requirements clarity audit evaluates feature requirement texts to ensure unambiguous planning instructions. It analyzes writing quality by checking for clear subjects, verbs, and single propositions, reducing rework and divergent interpretations during the design phase.

To audit requirements for writing quality, provide your active requirements document for textual analysis. The audit reviews the writing for clarity and conformity, generating an audit report that highlights ambiguities to resolve before planning begins.

A requirements clarity audit checks only text quality and writing clarity, not implementation logic. It strictly evaluates whether the requirement wording contains a clear subject, verb, and single proposition to prevent ambiguous planning instructions.

You should run a requirements review early in your forward planning workflow, specifically before planning and design phases. Applying the textual clarity audit at this stage prevents downstream rework by resolving ambiguous instructions before development starts.

You need to provide your active requirements markdown document for the writing quality audit. Supplying the requirements text allows the audit to analyze sentence structure and generate the corresponding clarity audit report.

This clarity audit targets feature requirements specifically rather than general documentation. It focuses on verifying that planning instructions contain a single proposition, clear subject, and verb to ensure unambiguous forward planning.