Hi Vinicius,
From a functional and QA perspective, one thing that helps is making the gaps visible before they become development assumptions.
I would keep a concise list separating confirmed requirements, assumptions awaiting validation, and open dependencies. For each pending item, I would record the owner, target date, affected journey, and impact if it remains unresolved.
For example, "API pending" is too broad. I would specify whether we are missing the response structure, a business rule, credentials, or test data, because each blocks a different activity.
I also find it useful to define acceptance scenarios while reviewing the flow. Questions such as "What happens if the API returns no records?", "What if the customer remains silent?" and "Where does the second failed attempt lead?" often expose missing requirements before implementation.
A short functional-to-development walkthrough can then check whether the specification, flow, and integration documentation describe the same behavior.
With a tight deadline, I would agree on what can proceed with validated information and what remains dependent on a decision. That gives the team a concrete basis for discussing delivery dates and changes.
The documentation can evolve during the project, but unresolved decisions need to stay visible and traceable.
------------------------------
Fabíola
------------------------------