What problem does it solve? Turning a loose feature idea into a structured requirements document is slow and error-prone, especially when the new feature must respect an existing legacy system. This Skill converts a free-form sentence or paragraph into a complete requirements.md file grounded in artifacts previously extracted from the codebase, while detecting and safely handling features already in progress. ## Core Features & Use Cases - Requirements Generation: Reads reverse-engineering artifacts (architecture.md, domain.md, inventory.md, code-analysis.md) and writes a requirements.md following a project template, with confidence markers and at most three [DÚVIDA] ambiguity flags. - In-Progress Feature Detection: Inspects physical artifacts (requirements.md, roadmap.md, actions.md checkboxes) to determine the real stage of an existing feature and asks the user whether to continue it, pause it in parallel, or abandon it—never overwriting silently. - Hooks and State Management: Executes optional and mandatory before/after hooks from .reversa/hooks.yml and maintains .reversa/active-requirements.json with atomic writes. - Use Case: A developer types "/reversa-requirements add OAuth login to the legacy portal" and receives a fully cited requirements document in _reversa_forward/001-oauth-login/, plus a suggestion for the next pipeline step. ## Quick Start Type "/reversa-requirements" followed by a sentence describing the feature you want, and the Skill will produce a complete requirements document anchored in your project's reverse-engineering artifacts.
