Create engineering-handoff-issue

.github/ISSUE_TEMPLATE/engineering-handoff-issue.md

@@ -0,0 +1,46 @@
+---
+name: Design to Engineering Handoff Issue
+about: PMs use this template when a User Story is ready for Engineering. This will be a separate issue for Engineering to track their work.
+title: 'Engineering for #[add related user story issue number] [Related User Story Title]'
+labels: 'milestone: missing, points: missing, Role: missing, Complexity: Missing, Feature: Missing'
+assignees: ''
+
+---
+
+**UPDATE LABELS: Add the following labels to each new issue, and remove default labels. Then remove this section:**
+* Role
+* Feature
+* Points 
+* Complexity
+
+### Dependencies/Related Engineering issues
+
+#### Back End
+- 
+
+#### Front End
+- 
+
+#### Dev Ops
+- 
+
+### Overview
+This issue is for tracking engineering work related to #[add related user story issue number], which is [add short description of related user story]
+
+### Action Items
+- Assign and Prep
+  - [ ] Engineering Lead: Review User Story and Design and assign Engineer
+  - [ ] Engineer: Review User Story and Design
+  - [ ] Engineer: Work with PM and Design Lead to clarify any questions about the User Story
+  - [ ] Engineer/Engineering Lead: determine if work should be split into multiple issues, if so create those issues and link them in this issue. 
+- Draft and Review:
+   - [ ] [Add engineering action items here]
+   - [ ] Code is deployed, changes are visible in https://dev.homeunite.us/
+   - Let Product know that it is ready for review
+      - [ ] Engineer: Change Issue Status to "For Review/Feedback Needed"
+      - [ ] Engineer: Add Label "Ready for: Product"
+      - [ ] Engineer: Tag the PM (assignee) of the related User Story in a comment below and let them know that a draft is ready for review
+   - [ ] Product: Review https://dev.homeunite.us/ and compare against Acceptance Criteria
+   - [ ] Repeat above steps until all Acceptance Criteria in the User Story are accounted for
+
+### Resources/Instructions