Create project brief and add it to readme.md

[carodew]

The initial project brief should give newcomers everything they need to know to understand what this project is and why we're doing it.

it should include ...

• problem statement (what problem does the website solve?)
• project goal
• primary user groups, ranked

it's done when ...

• the team and stakeholders agree on it
• it's entered into the readme.md and merged to the master branch

[carodew]

We can draw inspiration for format from the Modular PM curriculum (on GSA's internal Google Drive, no public links available at this time).

Specifically – the decks titled "Framing the problem," "Setting the product vision."

Note there's no one right way to write a project brief (framing document, thing that describes what we're trying to build) so I'm open to including other sections, as long as we keep the lift pretty lightweight.

[carodew]

Closing! I miss our high five emoji here.