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.