reversa-audit

Cross-check requirements, roadmap, and actions to produce a severity-ranked inconsistency report.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-audit
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-audit
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds mismatches between a feature’s requirements, its roadmap decisions, and its implementation actions so issues can be resolved before moving forward.

Core Features & Use Cases

  • Strict cross-check coverage: Verifies that every functional requirement is represented in roadmap decisions, that roadmap decisions map to actions, and that Gherkin scenarios are covered by at least one decision or action.
  • Consistency and identifier validation: Checks naming consistency across documents, verifies that referenced IDs exist, and ensures contracts and referenced interfaces align with the roadmap.
  • Legacy-rule alignment: Flags decisions that contradict the legacy domain rules and architecture components described in the SDD.
  • Action sanity checks: Ensures dependencies point to existing IDs, detects invalid task target sharing, and looks for dependency cycles.
  • Safety-first output: Produces a severity-based report (CRITICAL/HIGH/MEDIUM/LOW) and does not alter analyzed artifacts.

Quick Start

Run reversa-audit to audit the current active feature by cross-checking requirements.md, roadmap.md, and actions.md and returning a severity-ranked inconsistency report.

Frequently Asked Questions about reversa-audit

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

FAQPage Schema
How do I audit feature requirements against roadmap decisions and actions?

Auditing feature inconsistencies involves cross-checking requirements, roadmap, and actions to find mismatches that block forward progress. The audit verifies naming consistency, identifier existence, and dependency cycles without modifying the analyzed artifacts.

Why does my feature roadmap have inconsistencies with implementation actions?

Feature roadmap inconsistencies arise when roadmap decisions lack corresponding implementation actions, when referenced identifiers do not exist, or when task dependencies form invalid cycles. A strict cross-check audit detects these mismatches and logs them by severity.

How do I check if Gherkin scenarios are covered by roadmap decisions?

To check Gherkin scenario coverage, run a cross-check audit that verifies every Gherkin scenario is represented by at least one roadmap decision or implementation action, flagging any missing coverage as an inconsistency in the audit report.

Can I validate legacy domain rules against current roadmap decisions?

You can validate legacy domain rules by running an audit that flags current roadmap decisions contradicting the legacy domain rules and architecture components described in the SDD, outputting findings categorized by severity into a cross-check report.

Does the cross-check audit modify my requirements and roadmap files?

The cross-check audit does not modify analyzed artifacts. It operates safely by reading the reverse state to locate folders and writing severity-based findings exclusively into a new cross-check.md file within the feature directory.