reversa-writer

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.

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.

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.

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.

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.

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.