reversa-reviewer

Review reverse-engineering specs and correct confidence classifications.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-reviewer-afsjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-reviewer
Source: https://github.com/afsjr/secretaria_escola_csm/tree/main/.agents/skills/reversa-reviewer
Command: npx skills add https://github.com/afsjr/secretaria_escola_csm --skill reversa-reviewer-afsjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It improves the quality and trustworthiness of engineering reverse specifications by detecting inconsistencies, correcting confidence levels, and producing human-validation questions.

Core Features & Use Cases

  • Spec consistency review: Checks each unit’s requirements.md, design.md, and tasks.md for internal contradictions and missing expected behaviors.
  • Cross-unit contradiction detection: Flags conflicts and missing units by comparing generated artifacts and expected module coverage.
  • Confidence classification with rules: Reclassifies items into 🟢 CONFIRMADO, 🟡 INFERIDO, or 🔴 LACUNA using the project’s confidence rules.
  • Human-in-the-loop validation: Generates _reversa_sdd/questions.md and processes user answers according to answer_mode.

Quick Start

Ask the reviewer agent to review the reverse-engineering specs in the <output_folder> and produce _reversa_sdd/confidence-report.md plus any validation questions needed to finalize gaps.

Frequently Asked Questions about reversa-reviewer

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

FAQPage Schema
How do I validate confidence levels in reverse-engineering specifications?

Reverse-engineering spec review detects inconsistencies and validates confidence by checking requirements, design, and tasks files for internal contradictions. It cross-references generated artifacts and expected module coverage to flag conflicts and missing units across the entire output folder.

What is a traceability matrix used for in spec review?

Human-in-the-loop validation in spec review generates a questions file for red gap classifications and processes user answers based on answer mode. This enforces confidence rules and finalizes missing expected behaviors without requiring full manual re-verification of the entire specification.

How do I generate questions for specification gaps during reverse engineering?

To generate questions for specification gaps, apply confidence rules to identify red lacuna classifications in the reviewed specs. The system automatically produces a dedicated questions file to prompt human validation and resolve missing expected behaviors in the reverse-engineering output.

Can I cross-review reverse specs with Codex integration?

Reverse spec review requires canonical unit files and global traceability artifacts in the output folder, along with a defined confidence rules reference file. These inputs provide the expected module coverage and classification criteria needed to detect contradictions and validate confidence.