Specifications and user stories must be, before anything else, clear, accurate and interpretation-neutral. When implementing features, developers must minimize the guesswork associated with formulating and understanding chunks of text. However, in practice, ambiguity is more often the rule rather than the exception. The presentation aims at offering an extensive set of rules and examples which can help developers and other IT professionals spot and prevent lack of clarity simply by looking at key words, phrases, and structural elements.