Vague Requests Cost More Than Slow Launches
"Add discount codes" is a wish, not a requirement.
A developer can build from it only when it also says:
1. Who it is for and what problem it solves.
2. What "done" looks like.
3. What happens when the code has expired.
4. What is out of scope for now.
5. Who answers questions when they get stuck.
Miss one and the developer guesses. Every guess is a small bet on rework.
Which of the five do your specs skip most often?