reversa-clarify

To resolve ambiguous requirements before planning, you can generate targeted clarification questions for vague phrasing and integrate the answers directly into the active requirements document. This removes uncertainty and reduces rework.

Handling missing edge scenarios involves generating up to five user questions to clarify undefined terms and gaps. The answers are integrated into an Esclarecimentos section while keeping the Lacunas section consistent.

Updating a requirements document after clarifying business rules requires atomic persistence edits to remove resolved markers and integrate answers. This updates the active feature document and produces a session report of remaining unresolved items.

Requirement clarification is needed during the forward cycle when your requirements contain explicit markers, vague phrasing, undefined terms, or missing negative and edge scenarios. It applies between the requirements and planning phases.

Yes, you can enforce before-clarify and after-clarify hooks via configuration files to manage state-based path resolution. This ensures atomic edits are applied correctly to the requirements document during the clarification process.