What problem does it solve? Reverse-engineering a legacy system often ends with scattered notes instead of actionable documentation. This Skill turns extracted knowledge about a legacy codebase into formal, traceable specifications organized as one folder per unit, each containing requirements.md, design.md, and tasks.md files detailed enough for an AI agent to reimplement the functionality. ## Core Features & Use Cases - Folder-per-unit spec generation: Creates requirements.md, design.md, and tasks.md per module, endpoint, use case, feature, or custom granularity defined in config.toml. - Confidence-tagged traceability: Marks every statement as confirmed, inferred, or a gap, and maps legacy files to spec units in a code-spec matrix. - Incremental, checkpointed workflow: Generates one file at a time with user confirmation, saves progress to state.json, and supports pause/resume across sessions. - Use Case: After analyzing a legacy monolith, run this Skill to produce per-module specification folders plus OpenAPI definitions, user stories, and a traceability matrix for a planned rewrite. ## Quick Start Ask the agent to generate the specification plan for the legacy project using the reversa writer, then type CONTINUAR to produce each file step by step.
