Verified:GitHub

reversa-quality

Audit feature requirements for clarity, completeness, and consistency before planning.

Updated Mar 31, 2026

Search Tags:#requirements #audit #documentation quality #planning readiness #gherkin scenarios #textual clarity #clarify ambiguity

Ready to run

npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-quality-afsjr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-quality
Source: https://github.com/afsjr/secretaria_escola_csm/tree/main/.agents/skills/reversa-quality
Command: npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-quality-afsjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you improve the textual quality of feature requirements so they can be turned into a plan and code without rework caused by unclear wording or missing information.

Core Features & Use Cases

Textual clarity audit: checks whether each statement has unambiguous meaning suitable for implementation planning.
Completeness and consistency checks: verifies required template sections, terminology consistency, and alignment with project principles.
Scenario quality validation: evaluates whether happy paths, edge cases, and coverage expectations are present in Gherkin-like scenarios, avoiding gaps in coverage.

Quick Start

Run the reversa-quality audit to generate requirements-audit.md after it reads .reversa/active-requirements.json and the active feature's requirements.md.

Frequently Asked Questions about reversa-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit feature requirements for textual clarity before coding?▼

To audit feature requirements for textual clarity, run a quality audit that checks each statement for unambiguous meaning, ensuring the requirements are ready for implementation planning and coding without rework.

What does a requirements completeness and consistency check include?▼

A requirements completeness and consistency check verifies required template sections, terminology consistency, and alignment with project principles to ensure textual quality before turning requirements into a plan and code.

How do I validate Gherkin scenarios for missing edge cases in requirements?▼

To validate Gherkin scenarios for missing edge cases, a scenario quality validation evaluates whether happy paths, edge cases, and coverage expectations are present, avoiding gaps in coverage before implementation.

Can I audit requirements without modifying the original requirements.md file?▼

Yes, you can audit requirements without modifying the original requirements.md file because the audit produces a structured report saved atomically to feature-dir/audit/requirements-audit.md, leaving the source document untouched.

What is the best way to prepare requirements for implementation planning?▼

The best way to prepare requirements for implementation planning is to perform a forward-cycle requirement review that eliminates unclear wording and missing information, producing a structured audit report for the next coding phase.

Why does my implementation plan fail due to ambiguous requirements?▼

Your implementation plan may fail due to ambiguous requirements because unclear wording and missing information in the requirements.md cause rework, which a textual clarity audit identifies before planning begins.