skills.rest
RLuf
RLufCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reversa-audit

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

Updated Jun 26, 2026
Search Tags:#consistency#specification#requirements#audit#read-only#cross-check#severity report
One-click install
npx skills add https://github.com/RLuf/fzagent --skill reversa-audit-rluf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-audit
Source: https://github.com/RLuf/fzagent/tree/main/.agents/skills/reversa-audit
Command: npx skills add https://github.com/RLuf/fzagent --skill reversa-audit-rluf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a feature is specified across three separate documents (requirements.md, roadmap.md, and actions.md), contradictions, coverage gaps, and phantom references easily slip in. 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 - Four-axis cross-check: Verifies coverage (every requirement maps to a roadmap decision and an action), consistency (terminology and identifiers match across documents), legacy coherence (no conflicts with existing domain rules and architecture), and actions sanity (valid dependencies, no cycles, no parallel file conflicts). - Severity-ranked report: Writes findings to feature-dir/audit/cross-check.md classified as CRITICAL, HIGH, MEDIUM, or LOW, with stable IDs (A001, A002, ...) and explanations for serious findings. - Strictly read-only guarantee: Never modifies requirements.md, roadmap.md, actions.md, or any other analyzed artifact; the only permitted write is the audit report itself. - Use Case: After drafting a feature's requirements, roadmap, and action plan with the reversa framework, run the audit to catch a requirement that never became a roadmap decision or a dependency cycle in the action list before implementation starts. ## Quick Start Type /reversa-audit to cross-check the requirements, roadmap, and actions documents of the active feature and generate the severity-ranked 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 action plan documents?▼

Run the reversa-audit skill with the /reversa-audit command while a feature is active. It reads requirements.md, roadmap.md, and actions.md, compares them across four axes, and writes a severity-ranked report to feature-dir/audit/cross-check.md.

What does the reversa-audit skill check for?▼

It checks coverage (every requirement maps to roadmap decisions and actions), consistency (matching terminology and valid identifiers), legacy coherence (no conflicts with existing domain rules), and actions sanity (valid dependencies, no cycles, no parallel file conflicts).

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, even if asked. Its only permitted write is the audit report at feature-dir/audit/cross-check.md.

Why does reversa-audit abort when I run it?▼

The audit aborts if .reversa/active-requirements.json is missing or if any of the three artifacts (requirements.md, roadmap.md, actions.md) does not exist. The abort message lists what is missing and which skill generates it.

How are findings classified in the audit report?▼

Findings are classified as CRITICAL (conflicts with legacy rules, broken contracts, dependency cycles), HIGH (uncovered requirements, phantom identifiers), MEDIUM (terminology mismatches), or LOW (cosmetic issues), each with a stable ID like A001.

When should I run reversa-audit in the development workflow?▼

Run it as an optional step in the forward phase after the requirements, roadmap, and actions documents exist but before coding. If CRITICAL or HIGH findings appear, review them manually before proceeding to the coding stage.

Related Skills

Explore More Software Engineering Skills→
Helcio-NogueiraHelcio-Nogueira

reversa-audit

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

Community
Intermediate
danielbaustindanielbaustin
4

repo-code-review

Identify high-risk areas across a repository with a findings-first code review.

Community
Advanced
Steve-Smith-CODESteve-Smith-CODE

speckit-clarify

Identify and resolve ambiguities in software feature specifications using a structured requirements taxonomy.

Community
Intermediate
latestaiagentslatestaiagents
5

ai-code-reviewer

Review AI-generated code for correctness, security, performance, and maintainability issues.

Official
Advanced