reversa-writer

Generate requirements.md, design.md, and tasks.md specifications per legacy unit.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-writer-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-writer
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-writer
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-writer-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The reversa-writer turns reverse-engineering outputs into formal, executable specifications that can be used to reimplement legacy behavior with traceability, reducing ambiguity during modernization.

Core Features & Use Cases

  • Generates operational specs per legacy unit: Produces a folder-per-unit structure with canonical files (requirements.md, design.md, tasks.md) tailored by the configured granularity.
  • Respects language and naming conventions: Outputs unit folder names in the configured doc_language and sanitizes names to be OS-safe.
  • Supports completeness via optional artifacts: Adds contracts, flows, edge cases, decisions, and traceability/openapi/user-stories globals when doc_level and context require them.

Quick Start

Use the reversa-writer skill to generate unit-by-unit specifications after reverse-engineering has populated .reversa/context/surface.json and .reversa/state.json.

Frequently Asked Questions about reversa-writer

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

FAQPage Schema
How do I generate executable specifications from legacy reverse engineering outputs?

You generate executable specifications by reading state.json and surface.json to produce unit-specific requirements.md, design.md, and tasks.md, ensuring traceability for legacy reimplementation.

What is a traceability matrix in legacy code modernization?

A traceability matrix in legacy modernization links reverse-engineered modules and endpoints to formal requirements and tasks, ensuring generated executable specs reduce ambiguity during reimplementation.

How do I create OpenAPI specs from reverse engineered endpoints?

You create OpenAPI specs from reverse-engineered endpoints by detecting interfaces during the generation phase, producing global OpenAPI artifacts alongside canonical requirements and design documentation based on configured doc levels.

Can I generate engineering documentation organized by unit folders?

Yes, engineering documentation can be organized by unit folders. The process enumerates targets from config files and creates sanitized, OS-safe folder names containing requirements, design, and task files tailored to your configured granularity.

What optional artifacts are generated for edge cases and user stories during reimplementation planning?

During reimplementation planning, optional artifacts generated include contracts, flows, decisions, and global user stories, added dynamically based on the detected doc level and specific interface context.

Does legacy spec generation support multiple languages for engineering documentation?

Yes, legacy spec generation supports multiple languages. It respects the configured doc_language setting to output unit folder names and formal executable specifications in the language defined by your reverse engineering configuration.