reversa-writer

Automates creation of executable system specifications for legacy systems from source code.

Updated Feb 27, 2026

Search Tags:#system analysis #reverse engineering #specification generation #code traceability #system specifications

Ready to run

npx skills add https://github.com/luisgustavooliveira/skills --skill reversa-writer-luisgustavooliveira

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-writer
Source: https://github.com/luisgustavooliveira/skills/tree/main/reversa-writer
Command: npx skills add https://github.com/luisgustavooliveira/skills --skill reversa-writer-luisgustavooliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of creating executable system specifications for legacy systems, with traceability to source code, OpenAPI, user stories, and code-spec matrix. It is useful in the reverse engineering analysis phase.

Core Features & Use Cases

Specs Generation: Automates the creation of specifications like SDD (System Design Document), OpenAPI, user stories, and code-spec matrix.
Traceability: Ensures that each spec is traceable back to the original source code.
Compatibility: Supports Claude Code, Codex, Cursor, Gemini CLI, and other compatible agents.

Quick Start

Use the reversa-writer skill to generate specifications for the system under analysis.

Frequently Asked Questions about reversa-writer

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

FAQPage Schema

How do I generate system specifications for legacy code?▼

You can generate system specifications for legacy code by using automation to extract design documents, OpenAPI definitions, and user stories directly from the existing source code. This ensures every generated spec is traceable back to the original implementation.

What is a code-spec matrix and how does it help reverse engineering?▼

A code-spec matrix is a mapping document that links generated system specifications directly to their corresponding source code components. It helps reverse engineering by providing clear traceability, ensuring you can verify how each documented behavior is implemented.

Can I generate OpenAPI specifications from an existing legacy system?▼

Yes, you can generate OpenAPI specifications from an existing legacy system by analyzing the source code structure and extracting API endpoints, request formats, and response schemas into a standardized, executable specification format.

Does this specification generation work with Cursor and Gemini CLI?▼

Yes, this specification generation process is compatible with Cursor and Gemini CLI, along with Claude Code and Codex. It integrates with these agents to automate the creation of system design documents and traceability matrices.

What is the best way to create a System Design Document from source code?▼

The best way to create a System Design Document from source code is to automate the extraction of architectural and behavioral patterns, generating an executable specification that includes user stories and a code-spec matrix for full traceability.

When do I need executable system specifications with traceability?▼

You need executable system specifications with traceability during the reverse engineering analysis phase of legacy systems, especially when you must validate generated user stories and design documents against the actual source code.