In an ideal world Checkstress would be a check on an existing fully populated calc file. Typically this includes FEM checks and gross -error checks on assumptions. In reality the CS phase is often used for a final iteration of the stressing, maybe using updated loads. If the original analysis is followed, incorporating the new loads as you go it also forms a check on the method. Any significant varaitions to the results are flagged as this may indicate an error somewhere.
I am not aware of any empirical requirements docuemnt for CS, Airbus issue their own CS stressing methods, i.e. methods that have to be used for CS otehrwise the results are not accepted. Sometimes an alternate method is submitted to the methods group, which can allow non-Airbus CS methods to get thru.
So, your CS list remains ellusive, l suggest that an ad-hoc requirement list would include: External loads, FEM validation, Internal loads, stressing methods, spreadsheet validation, assumption checks, inclusion of post-test factors, compliance checklist, RF summary and (if Airbus) production of ACD4 ACD6 and final stress dossiers, for the authorities.
I may have left something out, but its a start.