What problem does it solve? Reverse-engineered knowledge about legacy systems often stays scattered and informal, making it impossible to reimplement features faithfully. This Skill turns extracted legacy knowledge into formal, traceable operational contracts organized as folder-per-unit specifications. ## Core Features & Use Cases - Folder-per-unit spec generation: Creates requirements.md, design.md, and tasks.md for each unit, with granularity driven by config (module, endpoint, use-case, hybrid, feature, or custom). - Confidence-tagged traceability: Marks every statement as confirmed, inferred, or a gap, and produces a code-to-spec coverage matrix plus optional OpenAPI and user-story artifacts. - Incremental, checkpointed workflow: Generates one file at a time with user confirmation, saves progress to state.json, and suggests session breaks to preserve quality on large projects. - Use Case: After analyzing a legacy codebase with the Reversa pipeline, run this Skill to produce a complete specification set that an AI agent could use to reimplement each module without seeing the original code. ## Quick Start Ask the agent to generate the specification plan for the legacy project using the reversa-writer skill, then type CONTINUAR to produce each file step by step.