reversa-clarify

To clarify ambiguous feature requirements, you can use a clarification loop that detects markers like [DÚVIDA] in your requirements.md, generates up to five ranked multiple-choice or short-answer questions, and integrates your answers directly into the document.

Handling vague assumptions in software requirements documentation involves generating targeted follow-up questions that force precise decisions, then writing those answers back into a structured Esclarecimentos section while cleaning resolved items in place.

You update requirements.md by atomically writing answers into the ## Esclarecimentos section before ## Lacunas, ensuring that previously vague assumptions or explicitly marked doubts are cleaned and resolved in place.

Yes, requirement clarification can be automated by reading .reversa/state.json to track the active feature flow and applying before-clarify/after-clarify hook logic to manage the question generation and document update process.

You need to run a requirement clarification cycle during the forward phase between requirements gathering and planning, specifically when your requirements.md contains explicit [DÚVIDA] markers or vague assumptions that would undermine implementation planning.