reversa

Orchestrate multi-agent analysis of legacy systems to generate executable specifications.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-pabloprogramador23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa
Source: https://github.com/Pabloprogramador23/loja/tree/main/.agents/skills/reversa
Command: npx skills add https://github.com/Pabloprogramador23/loja --skill reversa-pabloprogramador23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orquestra a análise de sistemas legados coordenando agentes de IA para gerar especificações executáveis.

Core Features & Use Cases

  • Orquestra fluxos de trabalho multiagente (Scout, Archaeologist, Writer) para explorar, analisar e sintetizar especificações.
  • Gera especificações executáveis e artefatos de plano que podem ser consumidos por agentes subsequentes.
  • Use case: inicie a análise de um sistema legado e gere gradualmente um conjunto de especificações estruturadas.

Quick Start

Say 'reversa' to start the orchestrated analysis sequence.

Frequently Asked Questions about reversa

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

FAQPage Schema
How do I generate executable specifications from a legacy system using AI agents?

Legacy system analysis generates executable specifications by orchestrating multi-agent workflows that explore, analyze, and synthesize codebases into structured artifacts. It coordinates agents sequentially to produce a comprehensive specification set.

What is the best way to orchestrate multi-agent workflows for reverse engineering?

Multi-agent reverse engineering orchestration coordinates specialized agents like Scout, Archaeologist, and Writer to explore and synthesize specifications. It manages state safely via JSON files and generates plan artifacts for subsequent agents.

How do I start an orchestrated analysis sequence for a legacy codebase?

Start the orchestrated analysis sequence by invoking the command to initialize the multi-agent workflow. The system then coordinates stepwise execution, generating checkpoints and artifacts across agents throughout the session.

Does multi-agent legacy analysis support session-based state management?

Session-based state management is supported during legacy analysis through checkpoint generation and safe state files. It persists orchestration progress in a JSON state file and a Markdown plan to ensure stepwise execution continuity.

Can I use this orchestration approach to analyze any legacy system scale?

This orchestration approach applies to multi-step, session-based analysis of legacy systems regardless of scale. It generates executable specifications and plan artifacts by coordinating agents across checkpoints to manage safe state.

Why use multiple agents instead of a single agent for reverse engineering?

Multiple agents distinguish reverse engineering tasks by assigning specialized roles like Scout, Archaeologist, and Writer to explore, analyze, and synthesize respectively. This orchestrated stepwise approach generates structured executable specifications.