What a great team name!

Requirements

• Looks like the use cases are still languishing in .... GOOGLE DOCS! So I can't give you any feedback for them at this time.
• Make sure that your tests are connected to your use cases somehow. You could reference ticket numbers in comments, for instance. This way I can tell whether your use cases are all covered, and whether your tests are actually testing what they should be.
• Your tests look very nice!

some general hints for the use cases

• Make sure your use cases do not actually cover multiple things (eg. editing/deleting/adding a claim all in one use case). If use cases have some parts in common, then split that out into another use case, and then include it as a precondition (eg. "user has navigated to a claim via use case __"). Use your judgement when covering multiple user stories with a single use case.
• don't forget exceptions/alternate flows
• don't forget your pre/post-conditions

UI Mockup and Storyboard

• please make a wiki page that embeds all of the images. There are sooo many svg files. Please help me figure out what am looking at.
• Don't forget "comments describing the important elements" in your mockups
• Where do I start in the storyboard?
• your storyboard needs some extra information such as labels for transitions describing what the system has done etc.. You also need to describe what the user is trying to accomplish
• don't forget to check that use cases and mockups are consistent

Release Planning

Don't forget this!

Glossary

• glossary looks nice :)
• Don't forget to "provide a list of useful informational references or links to related or competitive products." I don't need anything too detailed there, less than ten links with a brief description of each is fine.