reversa-quality

To audit requirements for clarity, this Skill validates that sentences have a clear subject, verb, and single meaning. It reads your active feature requirements and generates a report flagging ambiguous text before you proceed to planning.

To validate requirements coverage, this Skill checks whether happy paths, unhappy paths, and edge cases are expressed in Gherkin. It evaluates scenario coverage within your requirements document to ensure all critical paths are documented.

A quality gate for feature requirements documentation is an automated checkpoint that verifies text clarity, template completeness, and terminology consistency before planning. This Skill applies that gate to ensure requirements are actionable without retraining.

To check for missing template sections, this Skill validates that all required sections in your requirements document are filled in. It reads the active feature requirements and reports any incomplete sections in the generated audit file.

Yes, you can use Gherkin scenarios alongside this Skill to verify consistency. It evaluates glossary term usage consistency across your requirements and ensures each rule respects the project's principles file before generating the audit report.

The best way to ensure requirements are actionable is to run a pre-planning audit that detects ambiguity, missing sections, and inconsistent terminology. This Skill writes a requirements-audit report to your feature directory to prevent rework downstream.