reversa-writer

Executable specifications are generated by applying reverse engineering to legacy knowledge, producing a folder-per-unit layout with requirements.md, design.md, and tasks.md for each identified module to ensure traceability and consistency.

Structuring reverse engineering documentation is best achieved by creating a folder-per-unit layout, placing the three canonical files—requirements.md, design.md, and tasks.md—inside each folder to align with the original codebase and maintain traceability.

Incremental generation is fully supported, allowing you to reuse existing artifacts and add new unit folders while preserving prior reverse engineering analysis and documentation work completed for other modules or contracts.

Templates are used to guarantee consistency and traceability across all generated unit specifications, ensuring that every folder-per-unit structure contains the standardized requirements.md, design.md, and tasks.md canonical files.

A folder-per-unit layout is needed when transforming legacy system knowledge into formal, executable specifications, ensuring that each identified module or contract has dedicated requirements, design, and task documentation.

Generating unit specs without preserving existing artifacts risks losing prior reverse engineering work; however, this approach supports incremental generation to safely reuse and build upon existing documentation without overwriting previous analysis.