What problem does it solve? Legacy systems rarely document why decisions were made, leaving business rules, state transitions, and permission logic buried in code and Git history. This Skill performs the interpretation phase of a reverse engineering analysis, recovering that implicit knowledge into structured documentation. ## Core Features & Use Cases - Git Archaeology: Analyzes commit history (fixes, refactors, reverts) to reconstruct retroactive Architecture Decision Records (ADRs). - Business Rule Extraction: Mines conditionals, validations, enums, constants, and TODOs to build a domain glossary and rule catalog. - State Machines & Permissions: Generates Mermaid state diagrams for entities with status fields and RBAC permission matrices. - Confidence Tagging: Marks every finding as confirmed, inferred, or a gap so downstream agents know what to trust. - Use Case: During a legacy modernization project, run this after the codebase inventory phase to produce domain.md, state-machines.md, permissions.md, and ADRs that feed the specification-writing phase. ## Quick Start Ask the agent to analyze the Git history and source code of the legacy project and generate the domain rules, state machines, permission matrix, and retroactive ADRs into the reversa output folder.
