diff --git a/.gitlab/issue_templates/new-feature.md b/.gitlab/issue_templates/new-feature.md
index ec08771641bcf5193ea4db45581bc85eb1a0a5b9..06ea401cf9bee0a1c46fa7fb3a4fa1ac4372f57c 100644
--- a/.gitlab/issue_templates/new-feature.md
+++ b/.gitlab/issue_templates/new-feature.md
@@ -18,43 +18,3 @@ You can reference external content (example, demo paper) listed in section "Refe
 
 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.
-...