reversa-audit

Audits requirements, roadmap, and actions documents for cross-artifact inconsistencies with severity-ranked findings.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-audit-lacsousa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-audit
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.agents/skills/reversa-audit
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-audit-lacsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a project maintains separate requirements, roadmap, and actions documents, contradictions and coverage gaps silently accumulate between them. This Skill performs a strict read-only cross-check of the three artifacts and produces a severity-ranked audit report so a human can resolve inconsistencies before implementation begins. ## Core Features & Use Cases - Cross-artifact consistency checking: Verifies coverage, terminology, identifier references, and dependency sanity across requirements.md, roadmap.md, and actions.md. - Severity-ranked reporting: Classifies every finding as CRITICAL, HIGH, MEDIUM, or LOW and writes a structured cross-check.md report with stable finding IDs. - Strictly read-only guarantee: Never modifies the audited artifacts; the only permitted write is the audit report itself. - Use Case: After generating a roadmap and action plan from requirements, run this audit to catch a requirement with no roadmap decision, a phantom identifier like RF-12 that does not exist, or a dependency cycle before coding starts. ## Quick Start Audit the current feature's requirements, roadmap, and actions documents and report any inconsistencies by severity.

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 this audit skill against the requirements.md, roadmap.md, and actions.md files in the feature directory. It verifies coverage, terminology, and identifier references across all three and writes findings to audit/cross-check.md.

What does a requirements traceability audit check?▼

It checks that every functional requirement maps to a roadmap decision, every decision maps to an action, identifiers referenced actually exist, dependencies have no cycles, and parallel tasks do not share target files.

Does the audit modify my requirements or roadmap files?▼

No. The skill is strictly read-only for requirements.md, roadmap.md, actions.md, and related artifacts. Its only permitted write is the cross-check.md report inside the feature's audit directory.

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 aborts if the active-requirements.json state file is absent.

How are audit findings prioritized by severity?▼

Findings are ranked CRITICAL for legacy rule conflicts or dependency cycles, HIGH for uncovered requirements or phantom identifiers, MEDIUM for terminology mismatches, and LOW for cosmetic issues.