[x] Ensure other areas of markdown are properly formatted.
[x] Requirements: Missing Brief Section. Example
The Brief is an executive summary of all elements listed within. This should boil down to one long paragraph, devoting one to two sentences to each of the sub-sections defined.
[x] Requirements: Please refine your audience a bit further. Currently you're primary audience could be both an entrepreneur looking to buy and flip a house and also someone with no money to put down on a house and is using government funding to get a section 8 place? These two people would be looking for completely different experiences within your application. By more clearly defining your audience a lot of design choices will be more apparent for you to make.
[x] This (PROBLEM related) problem is oversimplified. It does do the trick but you might benefit from a stronger exploration of the problem your audience is having.
[x] Requirements: This (SOLUTION related) statement does not encompass the entirety of the application that you are developing. Touch on the features that you will develop to meet the needs of the user. You are not currently discussing the purpose of your app, why it would be used, and even how it allows for searching of property information.
[x] UVP: This application is separated
Poor phrasing, separated from what?
[x] Spec Feature Definitions: Requirements: Features should link out to your Issues and the routing information should be captured in a section specific to Routing, not feature definitions.
[x] Sitemap: Requirements: This is very hard to interpret.
[x] Interface: Requirements: Homepage should also have content that describes your value proposition that explains why users should use your service, or at least what benefit your service offers to users.
[x] Integrations: Your items here should be listed under Technical Requirements. Integrations would be 3rd party elements that you have no control over but are using. Like you are getting info from a 3rd party API. Sorry for the confusion of this.
[x] currentListing.json: Best Practice: Not Valid JSON. Should use double quotes around property keys, like the other properties within this file.
[x] Concurrently: Deployment Standards: Your implementation requires this installed globally, not locally.
[x] routes/property.js Best Practice: All Tokens should be hidden within environmental variables though it looks as if this may be for a hard coded test. If that is the case, understand that any other developer, or tester that has a user in their system to test with will have a different ID than the one that has been generated for your local machine. You need to think about other members of your team using this code base, as one of those members will be your live server, not just your local environment needs to work.
[x] models/Crime.js Best Practice: console.error for errors instead of .log as you are doing in other areas. Consistency counts.