reversa-audit

Cross-check requirements.md, roadmap.md, and actions.md for inconsistencies by severity.

1|Updated Nov 20, 2025

Search Tags:#requirements #audit #roadmap #reporting #artifact #actions #cross-check

Ready to run

npx skills add https://github.com/stribus/pygerengastos --skill reversa-audit-stribus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-audit
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-audit
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-audit-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditoria leitora estrita. Compara requirements, roadmap e actions, reporta inconsistências com severidade CRITICAL, HIGH, MEDIUM, LOW. JAMAIS altera os artefatos analisados. Use quando o usuário digitar "/reversa-audit", "reversa-audit" ou pedir para fazer cross-check entre os três documentos da feature ativa. Etapa opcional do ciclo forward.

Core Features & Use Cases

Verifica a consistência entre requirements.md, roadmap.md e actions.md.
Gera um relatório de inconsistências com severidades e recomendações para correção.
Suporta fluxo forward com verificação de estados e dependências.

Quick Start

Run a cross-check of requirements.md, roadmap.md, and actions.md to produce the human-ready audit report.

Frequently Asked Questions about reversa-audit

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

FAQPage Schema

How do I cross-check requirements, roadmap, and actions documents for feature alignment?▼

To cross-check requirements, roadmap, and actions documents for feature alignment, run an audit that compares the three artifacts and generates a report highlighting inconsistencies by severity. The process requires core artifacts to exist and reads state files to determine output folders.

What is a forward audit for feature consistency?▼

A forward audit for feature consistency is an optional workflow step that identifies inconsistencies among requirements.md, roadmap.md, and actions.md. It reports misalignments categorized by severity levels like CRITICAL, HIGH, MEDIUM, and LOW.

Do I need specific state files to run a document consistency audit?▼

Yes, running a document consistency audit requires reading .reversa/state.json and .reversa/active-requirements.json to determine output folders. The audit also enforces that core artifacts like requirements.md, roadmap.md, and actions.md exist before processing.

Why does my feature audit report show CRITICAL inconsistencies?▼

A feature audit report shows CRITICAL inconsistencies because the cross-check process evaluates requirements, roadmap, and actions documents, classifying severe misalignments under CRITICAL, HIGH, MEDIUM, or LOW severity to help prioritize corrections.

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

No, the cross-check audit operates under a strict read-only policy and will never modify the analyzed artifacts. It only reads requirements.md, roadmap.md, and actions.md to generate a human-ready report of inconsistencies.