reversa-writer

Generate requirements, design, and task documents from legacy codebases.

Updated May 19, 2026
One-click install
npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-writer-silaslopes100
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-writer
Source: https://github.com/silaslopes100/lojacarmenedaniel/tree/main/.agents/skills/reversa-writer
Command: npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-writer-silaslopes100

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the challenge of documenting legacy systems by automatically generating structured, executable technical specifications that ensure consistency and traceability.

Core Features & Use Cases

  • Standardized Documentation: Automatically creates requirements.md, design.md, and tasks.md for every system unit.
  • Traceability Matrix: Maps legacy code files directly to new specifications to ensure 100% coverage.
  • Use Case: When performing a system migration, use this Skill to parse your legacy codebase and generate a complete, modular documentation set that allows a new team to reimplement the system with high fidelity.

Quick Start

Use the reversa-writer skill to generate the technical specification documents for the identified modules in the current project.

Frequently Asked Questions about reversa-writer

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

FAQPage Schema
How do I generate technical specifications from legacy code for system migration?

Technical specifications from legacy code are formal, traceable documents generated by parsing the codebase into a modular structure. They map legacy files to new specifications, ensuring 100% coverage and enabling AI-assisted reimplementation without direct access to the original source.

Can I automatically map legacy code files to new requirements documentation?

Yes, you can automatically map legacy code files to new requirements using a traceability matrix. This matrix directly links legacy source files to the generated specifications, ensuring complete coverage and consistent traceability across the entire system migration process.

What is the best way to document an undocumented software architecture for a new team?

The best way to document undocumented software architecture is generating modular specification sets including requirements, design, and task files for every system unit. This structured approach provides high-fidelity documentation needed for accurate system reimplementation.

Does this approach work for reverse-engineering specifications from any legacy codebase?

Yes, reverse-engineering specifications works for any legacy codebase by using a modular unit structure to parse the existing system. It automatically creates structured, executable technical specifications that ensure consistency and traceability for software engineering teams.

Do I need direct access to the original source code to reimplement a system from specifications?

No, you do not need direct access to the original source code to reimplement a system if you have high-fidelity specifications. The generated requirements, design, and tasks documents provide sufficient detail to facilitate AI-assisted reimplementation independently.