Audit feature requirements text for clarity, completeness, and consistency.
npx skills add https://github.com/sandeco/reversa --skill reversa-quality-sandeco
Please help me install this Agent Skill. Skill: reversa-quality Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-quality Command: npx skills add https://github.com/sandeco/reversa --skill reversa-quality-sandeco
Reversa-quality improves how clear and complete your feature requirements are so they can be converted into an unambiguous execution plan by AI agents.
Run the reversa-quality skill after selecting the active feature so it audits the feature-dir/requirements.md and writes requirements-audit.md.
High-intent search queries and answers about installing and using this skill.
To audit requirements for clarity before AI planning, run an automated textual quality check on your requirements.md file to validate structure, scenario coverage, and glossary alignment. This generates a checklist-driven audit report to ensure your feature prose is unambiguous for agent execution.
AI agents generate ambiguous execution plans when feature requirements lack textual clarity, completeness, or consistency. Running a requirements-focused quality audit validates prose structure and Gherkin scenario coverage, ensuring the specification is unambiguous before forward-cycle planning and code generation.
Yes, you can validate Gherkin scenario coverage independently by running a requirements-focused textual quality audit. This checks writing quality, scenario coverage, and glossary alignment within the requirements.md file, producing an audit report without evaluating underlying implementation test coverage.
The best way to check if requirements are ready for forward-cycle AI agents is to run a quality hook that audits the active requirements file. This validates textual clarity, structure, and glossary alignment, then outputs a traceable requirements-audit.md report with an approval verdict and next-step guidance.
Yes, you must select an active feature and set the active state before auditing requirements quality. The audit process reads the active-requirements data to locate the feature-dir/requirements.md file, runs the before-quality hook, and atomically persists the requirements-audit.md report.
Markson22Audit requirements.md for clarity, completeness, and consistency, then write a structured audit file.
jesseotremblayCalculate TAM, SAM, and SOM market-size estimates using top-down and bottom-up methodologies.
ricardops34Audit feature requirements prose for ambiguity, missing sections, and inconsistent terminology.
nathan-a-kingEdit prose line by line to improve clarity, concision, and style.
