reversa-audit

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-audit-gleisonoliveira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-audit
Source: https://github.com/GleisonOliveira/dockerpilot-mcp/tree/main/.agents/skills/reversa-audit
Command: npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-audit-gleisonoliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a feature is specified across multiple planning artifacts (requirements.md, roadmap.md, actions.md), contradictions, coverage gaps, and phantom references silently accumulate. This Skill performs a strict read-only cross-check of those documents and produces a severity-ranked audit report so a human can fix issues before coding begins. ## Core Features & Use Cases - Cross-artifact consistency checks: Verifies coverage (every requirement maps to a roadmap decision and an action), terminology consistency, identifier validity, and alignment with legacy domain rules. - Severity-ranked reporting: Classifies findings as CRITICAL, HIGH, MEDIUM, or LOW and writes a structured cross-check.md report with stable finding IDs. - Strictly read-only guarantee: Never modifies requirements, roadmap, actions, interfaces, or any analyzed artifact; the only permitted write is the audit report itself. - Use Case: After generating requirements, roadmap, and action plans for a new feature, run this audit to catch a requirement with no corresponding action or a dependency cycle before developers start implementation. ## Quick Start Ask the agent to 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, which compares requirements.md, roadmap.md, and actions.md across coverage, consistency, legacy coherence, and dependency sanity axes. It writes a cross-check.md report listing every finding with a severity level.

What does the reversa audit report contain?▼

The cross-check.md report contains a header with the feature identifier, a summary count of findings by severity, a table of findings with IDs like A001, explanations for CRITICAL and HIGH issues, and a list of checks that passed.

Can the audit skill fix the inconsistencies it finds?▼

No. The skill is strictly read-only and never modifies requirements, roadmap, actions, or any analyzed artifact. For corrections it directs you to a clarification skill or manual editing, and only suggests the direction for fixes.

What happens if requirements or roadmap files are 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 severity levels assigned in the audit?▼

CRITICAL covers conflicts with legacy rules, broken external contracts, and dependency cycles. HIGH covers uncovered requirements and phantom identifiers. MEDIUM covers terminology mismatches, and LOW covers cosmetic issues.