initial

.gitlab/issue_templates/Implementation.md

@@ -0,0 +1,37 @@
+<!--
+Implementation issues are used break-up a large piece of work into small, discrete tasks that can
+move independently through the build workflow steps. They're typically used to populate a Feature
+Epic. Once created, an implementation issue is usually refined in order to populate and review the
+implementation plan and weight.
+-->
+
+## Relevant links
+
+<!--
+Information that the developer might need to refer to when implementing the issue.
+
+Basically a list of issues (bugs that are fixed, features implemented, etc. pp.)
+-->
+
+## Non-functional requirements
+
+<!--
+Add details for required items and delete others.
+-->
+
+- [ ] Documentation:
+
+## Verification steps
+
+<!--
+Add verification steps to help team members test the implementation. This is particularly useful
+during the ~"workflow::verification" step. You may not know exactly what the
+verification steps should be during issue refinement, so you can always come back later to add
+them.
+
+1. Check-out the corresponding branch
+1. ...
+1. Profit!
+-->
+
+/label ~"workflow::refinement" /milestone %Backlog