Don’t just use the first set of examples directly, refine the specification from them.

To get the most out of the examples, the resulting specification should be precise and testable, self-explanatory, focused, in domain language, and about business functionality.
Avoid scripts and talking about software design in specifications.
Don’t try to cover every single case. Specifications aren’t replacements for combinatorial regression testing.
Start with one example for each important set of cases and add examples that illustrate particular areas of concern to programmers and testers.
Define and use the Ubiquitous Language in specifications, software design, and tests.

Specification by Example (SBE) How successful teams deliver the right software