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 align with an existing legacy codebase. This Skill converts a free-form natural-language description into a complete requirements.md file grounded in artifacts extracted from the legacy system. ## Core Features & Use Cases - Context-anchored requirements: Reads reverse-engineering artifacts (architecture.md, domain.md, inventory.md, code-analysis.md, addenda) and cites them inside the generated requirements document. - In-progress feature detection: Inspects physical artifacts to detect an unfinished feature and asks the user whether to continue it, pause it, or abandon it before writing anything. - Doubt markers and self-validation: Marks ambiguous points with [DÚVIDA] tags (max three) and iteratively self-checks the document against a quality template up to three times. - Use Case: A developer types a one-paragraph idea for a new billing feature; the Skill creates _reversa_forward/001-billing/requirements.md with sections filled from the legacy system's documented domain rules, ready for the clarify and plan stages. ## Quick Start Run the reversa-requirements skill with a short paragraph describing the feature you want, and it will produce a requirements.md file inside a new feature directory under the forward folder.
