diff --git a/.gitlab/issue_templates/new-feature-with-design.md b/.gitlab/issue_templates/new-feature-with-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..ec08771641bcf5193ea4db45581bc85eb1a0a5b9
--- /dev/null
+++ b/.gitlab/issue_templates/new-feature-with-design.md
@@ -0,0 +1,60 @@
+# Proposers
+
+- name-of-proposer-1 (institution-of-proposer-1)
+- name-of-proposer-2 (institution-of-proposer-2)
+...
+
+# Description
+
+Describe your proposal in ~1000 characters.
+You can reference external content listed in section "References" as [Ref-1].
+
+# Demo or definition of done
+
+Describe which high level conditions needs to be fulfilled to demonstrate this feature implementation is completed.
+You can reference external content (example, demo paper) listed in section "References" as [Ref-2].
+
+# References
+
+1. [Reference name](https://reference-url)
+2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.
+
+# Feature Design (for New-Features)
+
+## Clarifications to Expected Behavior Changes
+
+Existing component logic and workflows between components that need to be altered to realize this feature.
+Remember to justify these changes.
+...
+
+## References
+
+List of relevant references for this feature.
+...
+
+## Assumptions
+
+Enumerate the assumptions for this feature, e.g., fix XXX is implemented and merged, specific configurations, specific
+components deployed.
+...
+
+## Impacted Components
+
+List of impacted components: Context, Device, Service, PathComp, Slice, Monitoring, Automation, Policy, Compute, etc.
+Just an enumeration, elaboration of impacts is done below.
+
+## Component1 Impact
+
+Describe impact (changes) on component1.
+...
+
+## Component2 Impact
+
+Describe impact (changes) on component2.
+...
+
+## Testing
+
+Describe test sets (unitary and integration) to be carried out.
+This section can include/reference external experiments, demo papers, etc.
+...