reversa-clarify

To resolve ambiguities in requirements, generate up to five targeted questions addressing unclear points, then integrate the answers directly back into your requirements document to ensure clarity before planning.

Yes, you can integrate clarification answers directly into a requirements.md file. This ensures that resolved ambiguities are documented in context, keeping the requirements file updated for downstream planning.

Yes, the Reversa framework supports requirements clarification during the forward engineering phase by generating targeted questions to resolve open points before proceeding to implementation.

The best way to identify open questions is to analyze the requirements document for ambiguities and automatically generate up to five targeted questions to clarify those undefined points before moving forward.

You can use compatible coding agents like Claude Code, Codex, Cursor, or Gemini CLI to automate requirements clarification, ensuring your environment supports these tools for generating and integrating questions.

You should not use automated requirements clarification if your requirements are already fully defined and unambiguous, or if you are outside the forward engineering phase where targeted question generation is optimized.