reversa-quality

Audit feature requirements for clarity, completeness, and consistency.

Updated May 13, 2026

Search Tags:#planning #requirements #clarity #governance #gherkin #text audit #reversa

Ready to run

npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-quality-cliffthelin

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It verifies that a feature's requirements are written clearly and completely enough to be converted into an actionable plan, reducing ambiguity and rework later.

Core Features & Use Cases

Textual clarity audit: Assesses whether the prose is unambiguous and well-structured for planning.
Completeness and consistency checks: Ensures required template sections are present and glossary terms are used consistently.
Scenario and edge-case coverage: Confirms that Gherkin scenarios include happy paths, sad paths, and relevant edge cases, without drifting into implementation/testing concerns.
Principles alignment: Reviews the requirements against the project’s reversa principles rules.

Quick Start

Use the reversa-quality skill when you want to review the quality of your active feature’s requirements before planning, for example by asking an AI to run the /reversa-quality command.

Frequently Asked Questions about reversa-quality

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

FAQPage Schema

How do I audit requirements for clarity before converting them into a plan?▼

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.

What does a requirements quality audit check for in Gherkin scenarios?▼

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.

Do I need a specific workspace setup to run a requirements text audit?▼

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.

When should I not use a requirements clarity audit?▼

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.

How do I verify my feature requirements align with project governance principles?▼

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.