Update ---epic.md

.github/ISSUE_TEMPLATE/---epic.md

@@ -6,24 +6,43 @@ labels: Epic, Product Note
 assignees: Nikhil-Nandagopal
 ---
 
-## Problem statement
+# Objective
-
+Here you fill in the objective of the feature/product that you are writing about.
-Why is this needed?
-What does it hope to achieve?
 
 ## Related issues
-
 [ ] #issue1
 
-## Success criteria
+# Success Metrics
+List of all metrics you are tracking and the desired goal.
+| Goal  | Metric |
+| ------------- | ------------- |
+| e.g. Simplify user experience  | Customer satisfaction score increases  |
+| e.g. Simplify onboarding flow  | Decrease churn rate down to 30% |
 
-How will we know the project succeeded?
+# Assumptions
+List any assumptions that you have about your users, technical constraints, or business goals (e.g., Most users will access this feature from tablet).
 
-## User story
+- Assumption 1
+- Assumption 2
+- Assumption 3
 
-How does a user use this feature? How does it relate to the problem?
+# Requirements
+| Requirement   | User Story | Importance | Notes |
+| ------------- | ------------- | ------------- | ------------- |
+| e.g. Must be mobile responsive  | e.g. as a user, I want to be able to access the platform via mobile phone  | High, Low or Medium  | Content Cell  |
+| e.g. The user should be able to leave a comment | e.g as a user, I want to be able to communicate with the other members on the canvas  | High, Low or Medium  | Content Cell  |
 
-## Details
+# Out of Scope
+List the things that are out of cope or might be revisited after the first release.
+- Item 1
+- Item 2
+- Item 3
 
-What are the specifications of the implementation?
+# Developer Handoff Document in Figma
-Product notes, designs etc.
+Link to the developer Handoff Document: 
+
+# Questions
+| Question  | Answer | Date Answered |
+| ------------- | ------------- | ------------- |
+| e.g. How might we ensure that the comments section doesn't cover the canvas | Content Cell  | Content Cell  |
+| Content Cell  | Content Cell  | Content Cell  |