From b6c5cb9158bf375e4690486052b8f60148e313d8 Mon Sep 17 00:00:00 2001
From: subhajitlucky <subhajitpradhan310@gmail.com>
Date: Wed, 13 May 2026 10:08:20 +0530
Subject: [PATCH 1/2] docs: add feature acceptance criteria

---
 README.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 8a32bc4..f6a4ad6 100644
--- a/README.md
+++ b/README.md
@@ -1 +1,9 @@
-This is open issue repo!~
\ No newline at end of file
+This is open issue repo!~
+
+## Feature Acceptance Criteria
+
+Use this checklist for feature issues and pull requests:
+
+- Describe the expected user-facing behavior.
+- Include the files or screens affected by the change.
+- Add verification notes showing how the change was tested.

From 7cd514f86e7100fed80a4c8e3d6227bfec3adce8 Mon Sep 17 00:00:00 2001
From: subhajitlucky <subhajitpradhan310@gmail.com>
Date: Wed, 13 May 2026 10:22:11 +0530
Subject: [PATCH 2/2] feat: add feature acceptance issue form

---
 .../feature_acceptance_criteria.yml           | 41 +++++++++++++++++++
 README.md                                     |  2 +-
 2 files changed, 42 insertions(+), 1 deletion(-)
 create mode 100644 .github/ISSUE_TEMPLATE/feature_acceptance_criteria.yml

diff --git a/.github/ISSUE_TEMPLATE/feature_acceptance_criteria.yml b/.github/ISSUE_TEMPLATE/feature_acceptance_criteria.yml
new file mode 100644
index 0000000..6dc3209
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_acceptance_criteria.yml
@@ -0,0 +1,41 @@
+name: Feature acceptance criteria
+description: Request a feature with clear acceptance criteria.
+title: "[Feature]: "
+labels:
+  - Feature Bug
+body:
+  - type: textarea
+    id: summary
+    attributes:
+      label: Feature
+      description: Describe the feature or behavior you want.
+      placeholder: Add the user-facing behavior this feature should provide.
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance-criteria
+    attributes:
+      label: Acceptance Criteria
+      description: List the conditions that must be true for this feature to be complete.
+      placeholder: |
+        - Users can...
+        - The UI/API shows...
+        - Errors are handled by...
+    validations:
+      required: true
+  - type: textarea
+    id: affected-areas
+    attributes:
+      label: Affected Areas
+      description: Note the files, screens, APIs, or workflows expected to change.
+      placeholder: README, issue templates, UI screen, API route, etc.
+    validations:
+      required: false
+  - type: textarea
+    id: verification
+    attributes:
+      label: Verification
+      description: Describe how maintainers can verify the feature.
+      placeholder: Add manual checks, commands, screenshots, or expected output.
+    validations:
+      required: false
diff --git a/README.md b/README.md
index f6a4ad6..9118a11 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@ This is open issue repo!~
 
 ## Feature Acceptance Criteria
 
-Use this checklist for feature issues and pull requests:
+Use the feature issue form when opening feature work. Each request should include:
 
 - Describe the expected user-facing behavior.
 - Include the files or screens affected by the change.