feat(issue-labels): generate a standard set of labels to categorize issues

[gregswindle]

1. Issue type

⌦ Type the letter "x" in the "checkbox" the best describe this issue.

• Feature: I'm requesting a product enhancement.

2. User story summary

⌦ Describe what you want to accomplish, in what role/capacity, and why it's important to you.

EXAMPLE:
As a Applicant,
I want to submit my resume
In order to be considered for a job opening.

As a {role},
I must/need/want/should {do something}
In order to {achieve value}.

3. Acceptance criteria

⌦ Replace the examples below with your own imperative, "true/false" statements for the behavior you expect to see, or the behavior that would be true if there were no errors (for defects).

• 1. Job Applicants receive a confirmation email after they submit their resumes.
• 2. An Applicant's resume information isn't lost when errors occur.
• 3. {criterion-three}
• 4. {criterion-four}

🐞 4. Steps to reproduce (for defects only)

⌦ Provide a link to a live example, or
⌦ Replace the examples below with an unambiguous sequence of instructions that end with proof of the defect.
⌦ Include source code and log files, if relevant and available.

1. Enter the words "...." into the "Search" text field.
2. Select the Search button.
3. Next...
4. Then...
5. Finally...
6. X does not work as expected.

🐞 5. Your environment (for defects only)

⌦ Include as many relevant details about the environment in which the defect occured.

• Version of generator-community:
• Environment name and version (e.g. Chrome 39, node.js 5.4):
• Operating System and version (desktop or mobile):
• Link to your project: