reversa-clarify

Requirement de-ambiguation identifies undefined constraints and missing edge cases in active requirements, generating up to five ranked clarification questions. It processes vague language and missing details to ensure planning proceeds with fewer assumptions and reduced rework cycles.

You update requirements.md atomically by writing collected answers under the Esclarecimentos section and updating Lacunas. This requirements update loop preserves unresolved items while integrating clarified details directly into the active document.

State-driven context uses .reversa/state.json and .reversa/active-requirements.json to locate the correct feature and apply before-clarify hooks. This ensures clarification questions target the accurate active requirements context before generating outputs.

The maximum is five ranked, optioned questions generated for vague requirements. The Skill enforces this limit to keep the de-ambiguation process focused, ensuring stakeholders address only the most critical missing details or undefined constraints.

Yes, this clarification process applies to forward planning workflows where requirements contain [DÚVIDA] markers, vague language, or undefined constraints. It identifies these specific markers and missing edge cases to generate targeted clarification questions.