reversa-writer

To generate traceable operational specifications from legacy code, reversa-writer reads extracted state and context files, then produces per-unit folders containing requirements.md, design.md, and tasks.md for AI-driven reimplementation.

Folder-per-unit spec generation is an approach where each module, endpoint, or use-case gets its own output folder containing structured requirements, design, and task documents, enabling isolated and traceable analysis of legacy systems.

You control documentation completeness by setting the doc_level parameter, which conditionally adds optional artifacts like contracts.md, flows.md, edge-cases.md, decisions.md, and questions.md alongside the core spec files.

Yes, you can generate specifications by module, endpoint, use-case, hybrid structures, features, or custom folders, with the granularity governed by your config.toml and surface.json configuration files.

Yes, you need Reversa state files to generate operational specs. The tool requires .reversa/state.json, .reversa/config.toml, and .reversa/context/surface.json to determine unit scope, language, and output configuration.

Traceable specifications allow an AI agent to reimplement legacy functionality without accessing the original code by providing formal, structured requirements and design documents that map directly to extracted system knowledge.