Look at my white paper on Drools Design Patterns especially the section on Data Validation.
The section explains a strategy that circumvents the straightforward creation of one Drools rule per rule in the requirements. Simply put, you use data to describe these rules, insert the data as facts, along with the facts representing actual data, and write rules relating the descriptions to the data. You might say that the rules "interpret" the descriptions against the data.
There are adavantages and disadvantages to this approach, but it ought to be considered before launching into handwritten or spreadsheet rules.