[Too]

Unclear specifications in the edge cases is the definition of requirements engineering and the reason why such an approach usually isn’t the best for any moderately complex application.

If the person who wrote the requirements could formulate them precisely, they might as well have done it themselves in code rather than as requirements.

As a coder you just have to get used to it. Your job is to fill in the blanks so the higher ups can focus on the big picture.

This is why iterative planning (agile) has become so popular. You implement the most important use cases first and from there go through the edge cases together.