docs: define issue-first contribution workflow

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,7 @@
 name: Bug report
 description: Create a report to help us improve CrewAI
 title: "[BUG]"
-labels: ["bug"]
+labels: ["bug", "state:inbox"]
 assignees: []
 body:
   - type: textarea
@@ -30,6 +30,13 @@ body:
       description: A clear and concise description of what you expected to happen.
     validations:
       required: true
+  - type: textarea
+    id: impact
+    attributes:
+      label: Impact
+      description: Describe who is affected and how this problem affects their work.
+    validations:
+      required: true
   - type: textarea
     id: screenshots-code
     attributes:
@@ -106,6 +113,14 @@ body:
       description: Have a solution in mind? Please suggest it here, or write "None".
     validations:
       required: true
+  - type: textarea
+    id: verification-plan
+    attributes:
+      label: Verification plan
+      description: Describe how a maintainer can confirm that a future fix resolves the problem.
+      placeholder: Include a minimal reproduction, expected assertions, or a manual verification procedure.
+    validations:
+      required: true
   - type: textarea
     id: additional-context
     attributes:

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,7 +1,7 @@
 name: Feature request
 description: Suggest a new feature for CrewAI
 title: "[FEATURE]"
-labels: ["feature-request"]
+labels: ["feature-request", "state:inbox"]
 assignees: []
 body:
   - type: markdown
@@ -26,8 +26,8 @@ body:
   - type: textarea
     id: problem
     attributes:
-      label: Is your feature request related to a an existing bug? Please link it here.
-      description: A link to the bug or NA if not related to an existing bug.
+      label: Problem statement
+      description: Describe the user problem or unmet need without prescribing an implementation.
     validations:
       required: true
   - type: textarea
@@ -44,6 +44,30 @@ body:
       description: A clear and concise description of any alternative solutions or features you've considered.
     validations:
       required: false
+  - type: textarea
+    id: scope
+    attributes:
+      label: Proposed scope and non-goals
+      description: Describe what should be included and what should intentionally remain out of scope.
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance-criteria
+    attributes:
+      label: Acceptance criteria
+      description: List the observable outcomes that would make this request complete.
+      placeholder: |
+        - [ ] A user can ...
+        - [ ] Existing behavior remains ...
+    validations:
+      required: true
+  - type: textarea
+    id: verification-plan
+    attributes:
+      label: Verification plan
+      description: Describe the automated or manual checks that should confirm the feature works.
+    validations:
+      required: true
   - type: textarea
     id: context
     attributes:
@@ -62,4 +86,4 @@ body:
         - I can test the feature once it's implemented
         - No, I'm just suggesting the idea
     validations:
-      required: true
+      required: true