Add default issue templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug Report
+about: Create a new issue for a problem or bug
+title: ''
+labels: 'bug'
+assignees: ''
+
+---
+
+# Bug/Issue
+
+<!-- uncomment sections that might provide value for your particular issue -->
+
+## What was the problem?
+
+<!-- enter description or expected/actual behavior -->
+
+<!--
+## Reproduction steps
+
+1. Step 1
+1. Step 2
+-->
+
+<!--
+## Environment
+
+* URL:
+* Device: mobile/desktop
+* OS:
+* Browser:
+-->
+
+<!--
+## Screenshots
+
+-->

.github/ISSUE_TEMPLATE/story.md

@@ -0,0 +1,31 @@
+---
+name: New User Story
+about: Create a new issue in using the "user story" format.
+title: ''
+labels: 'story'
+assignees: ''
+
+---
+
+## Story
+
+As a ***TYPE_OF_USER***,
+I would like to ***NEW_FUNCTIONALITY***,
+So that I can ***ACCEPTED_OUTCOME***
+
+## Solution
+
+<!-- Propose a solution - This is subject to change as deemed by the implementers! -->
+
+```[tasklist]
+### Tasks
+- [ ] One task
+- [ ] Another task
+```
+
+## Acceptance Criteria
+
+<!-- Define acceptance criteria for ACCEPTED_OUTCOME -->
+
+- [ ] One criteria
+- [ ] Another criteria

.github/pull_request_template.md

@@ -0,0 +1,38 @@
+<!-- Uncomment and update the sections you need for your PR! -->
+
+# 🎫 Addresses issue: #0
+<!--
+Insert the issue number (or full link if the issue is in a different repo
+-->
+
+## 🛠 Summary of changes
+
+<!--
+Write a brief description of what you changed. Bulleted lists are perfect
+-->
+
+<!--
+## 📜 Testing Plan
+
+How would a peer test this work?
+
+- Step 1
+- Step 2
+- Step 3
+-->
+
+<!--
+## 👀 Screenshots and Evidence
+
+If relevant, include a screenshot or screen capture of the changes.
+
+<details>
+<summary>Before:</summary>
+
+</details>
+
+<details>
+<summary>After:</summary>
+
+</details>
+-->