reversa-clarify

To resolve ambiguous requirements before planning, you can generate targeted clarifying questions and write the answers directly back into the active requirements document. This updates vague sections and missing edge cases atomically.

Requirements clarification and gap analysis is the process of detecting ambiguity drivers like vague wording or open points in a requirements file, then generating prioritized questions to fill those gaps before development planning begins.

You update a requirements document with answers by applying clarifying hooks, rewriting affected requirement sections atomically, and creating an Esclarecimentos section while updating the Lacunas gap section accordingly.

You need to run a requirements clarification process during forward cycle planning, specifically after generating initial requirements and before creating a plan, when the requirements include open points or doubt markers.

Yes, you can use automated question generation for requirements updating without external dependencies. The skill operates standalone by reading local state files and applying internal taxonomies to produce prioritized clarifying questions.

If requirements still have gaps after a clarification pass, the system outputs a final status report recommending another round of clarification to resolve remaining open points before proceeding to the planning phase.