reversa-clarify

To resolve ambiguous requirements, you generate targeted clarification questions that identify vague phrases and undefined terms in your requirements documentation. This process asks up to five ranked questions to uncover missing details and obvious coverage gaps before forward planning begins.

Generating clarification questions involves scanning your active requirements document for [DÚVIDA] markers and obvious coverage gaps. The system ranks these ambiguities by their impact on the eventual plan, producing no more than five targeted questions to ensure critical forward planning decisions are resolved.

You update a requirements document by integrating answers into the appropriate ## Esclarecimentos section and removing resolved [DÚVIDA] entries from ## Lacunas. This direct requirements update ensures your active feature documentation remains accurate and free of open points.

Yes, you need an active-requirements.json file and a valid state.json for folder paths to resolve ambiguities. The workflow validates these prerequisites and applies before-clarify hooks before generating targeted questions for your requirements documentation.

Your requirements clarification process stops when state.json folder paths are missing or active-requirements.json existence validation fails. The system enforces these prerequisites and applies before-clarify hooks before it can generate ranked questions and update your active feature requirements.

Yes, you can use targeted question generation for requirements documentation in a forward-cycle workflow. It applies specifically to scenarios between requirements and planning phases, applying hooks orchestration to merge answers directly into your active document and remove existing gaps.