reversa-writer

Name: reversa-writer
Availability: InStock
Author: Ricardo

Generate executable specification artifacts from reverse-engineered legacy knowledge.

Updated May 16, 2026

Search Tags:#openapi #spec generation #task planning #traceability #engineering reversa #unit-based documentation #legacy reconstruction

Ready to run

npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-writer

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It converts reverse-engineered legacy knowledge into formal, traceable, executable specifications so teams can reimplement functionality reliably.

Core Features & Use Cases

Generates specs in a unit-based folder layout that includes requirements.md, design.md, and tasks.md, matching the configured granularity and language.
Orchestrates output based on reverse-engineering artifacts like state.json, config.toml, context surface.json, and outputs from prior agents.
Supports operational traceability and contract-level documentation by optionally generating contracts.md, flows.md, edge-cases.md, decisions.md, and global artifacts like openapi and traceability matrices.

Quick Start

Use the reversa-writer skill to generate the specification plan and then produce the first unit files into the configured output folder based on your existing reverse artifacts.

Frequently Asked Questions about reversa-writer

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

FAQPage Schema

How do I generate formal specifications from reverse-engineered legacy code?▼

Generating formal specifications from reverse-engineered legacy code involves transforming existing knowledge into executable artifacts using a unit-based folder layout. This process creates requirements.md, design.md, and tasks.md files for each configured module, endpoint, or feature unit.

What is engineering reverse workflow traceability and when do I need it?▼

Engineering reverse workflow traceability tracks the transformation of legacy knowledge into formal specs. You need it when reimplementing legacy functionality reliably, ensuring generated requirements, designs, and tasks maintain provenance from the original reverse-engineered artifacts.

How do I create an OpenAPI spec from existing reverse-engineered endpoints?▼

Creating an OpenAPI spec from reverse-engineered endpoints involves processing prior agent outputs and context surface data. This generates global artifacts including openapi documentation and traceability matrices, alongside unit-based requirements and design files for the configured endpoints.

Can I structure technical documentation by custom-defined units instead of modules?▼

Structuring technical documentation by custom-defined units is fully supported alongside modules, endpoints, use-cases, and features. The specification generation matches your configured granularity, outputting folder-per-unit structures containing requirements, design, and task files tailored to your specific unit definition.

Do I need prior reverse-engineering artifacts to generate executable specification plans?▼

Prior reverse-engineering artifacts are required to generate executable specification plans. The process depends on reading state.json, config.toml, context surface.json, and outputs from prior agents to correctly orchestrate the generation of formal, traceable specification artifacts.

What limitations exist when reconstructing legacy systems into executable specs?▼

Limitations when reconstructing legacy systems into executable specs include non-destructive behavior constraints and mandatory user confirmation checkpoints. The process cannot overwrite existing files without explicit approval, ensuring safe generation of requirements, design, and task artifacts within the configured output folder.