reversa-audit

Cross-checks requirements, roadmap, and actions documents and reports inconsistencies by severity.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill reversa-audit-helcio-nogueira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-audit
Source: https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026/tree/main/.agents/skills/reversa-audit
Command: npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill reversa-audit-helcio-nogueira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a feature is specified across three separate planning documents (requirements.md, roadmap.md, actions.md), contradictions, missing coverage, and broken references easily slip through. This Skill performs a strict read-only audit across all three artifacts and produces a severity-ranked report so a human can fix issues before coding begins. ## Core Features & Use Cases - Cross-document consistency check: Verifies coverage (every requirement maps to a roadmap decision and an action), terminology consistency, and valid identifier references across the three artifacts. - Legacy coherence validation: Confirms roadmap decisions do not contradict established domain rules and that cited architecture components actually exist. - Severity-ranked report: Writes findings to audit/cross-check.md classified as CRITICAL, HIGH, MEDIUM, or LOW, with stable IDs and suggested next steps. - Use Case: After generating requirements, roadmap, and actions for a new feature, run the audit to catch a requirement with no corresponding action or a dependency cycle before developers start implementation. ## Quick Start Ask the assistant to run reversa-audit to cross-check the requirements, roadmap, and actions documents of the active feature.

Frequently Asked Questions about reversa-audit

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

FAQPage Schema
How do I check consistency between requirements and a roadmap?▼

Run the reversa-audit skill, which compares requirements.md, roadmap.md, and actions.md across coverage, consistency, legacy coherence, and dependency sanity axes. It writes a severity-ranked report to the feature's audit/cross-check.md file.

What does the reversa-audit skill check in planning documents?▼

It verifies that every requirement maps to a roadmap decision and an action, that identifiers referenced actually exist, that terminology is consistent, that decisions do not contradict legacy domain rules, and that action dependencies have no cycles.

Does reversa-audit modify my requirements or roadmap files?▼

No. The skill is strictly read-only and never alters requirements.md, roadmap.md, actions.md, or any other analyzed artifact. Its only permitted write is the audit/cross-check.md report.

What happens if requirements.md or actions.md is missing?▼

The audit aborts with a message listing which artifacts are missing and which skill generates each one. It also reads .reversa/active-requirements.json first and aborts if that state file is absent.

How are audit findings classified by severity?▼

Findings are ranked CRITICAL (conflict with legacy rules, broken external contract, dependency cycle), HIGH (uncovered requirement, missing action, phantom identifier), MEDIUM (terminology inconsistency), and LOW (cosmetic issues).