reversa-detective

Extracts implicit business knowledge from legacy systems via ADRs, Git history, and state machines.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-detective-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-detective
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-detective
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-detective-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps interpret legacy systems by surfacing implicit business knowledge hidden in historical commits, ADRs, state machines, and RBAC matrices. It supports transformation of tacit domain insight into explicit, actionable documentation.

Core Features & Use Cases

  • Retroactive ADR extraction from Git history to capture business decisions.
  • Domain discovery from state machines, permissions, and legacy rules.
  • Guided interpretation of engineering reversals to inform modern design decisions.

Quick Start

Provide a guided interpretation of the legacy project to extract implicit business knowledge and generate domain documentation.

Frequently Asked Questions about reversa-detective

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

FAQPage Schema
How do I extract implicit business rules from legacy code?

Extract implicit business rules from legacy code by analyzing Git history, ADRs, and state machine definitions to surface tacit domain decisions and generate structured domain documentation.

What is the best way to reverse-engineer domain knowledge from Git history?

Reverse-engineering domain knowledge from Git history involves retroactively extracting ADRs and analyzing historical commits to capture business decisions and transform tacit domain insight into explicit artifacts.

Can I generate domain documentation from existing state machines and RBAC matrices?

Generate domain documentation from existing state machines and RBAC matrices by applying reverse-engineering analysis to interpret legacy rules and produce structured artifacts like domain.md and state-machines.md.

Does reverse-engineering legacy systems require existing ADR inputs?

Reverse-engineering legacy systems uses existing ADR inputs and governance context to guide the interpretation of engineering reversals and surface implicit RBAC mappings across the system.

How do I document tacit domain decisions for a modernization project?

Document tacit domain decisions for a modernization project by interpreting legacy state machines and permissions, producing structured domain artifacts to inform modern design decisions.