Add steps for searching GitHub Discussions and documenting related issues in the issue creation process

Author: hannesrudolph

.roomodes

@@ -465,6 +465,28 @@ customModes:
        </step>
 
        <step number="3">
+         <name>Search GitHub Discussions</name>
+         <instructions>
+           Search GitHub Discussions for related feature requests or bug reports:
+           
+           1. Use the GitHub web interface or API to search discussions in:
+              https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests
+           
+           2. Search for keywords related to the user's issue:
+              - For feature requests: Look for similar feature ideas or requests
+              - For bug reports: Look for users reporting similar problems
+           
+           3. Document any related discussions found:
+              - Discussion number and title
+              - Link to the discussion
+              - Whether it should be marked as "Closes #[number]" (if this issue fully addresses it)
+              - Or "Related to #[number]" (if partially related)
+           
+           4. If multiple related discussions exist, list them all for inclusion in the issue
+         </instructions>
+       </step>
+
+       <step number="4">
          <name>Explore Codebase for Context</name>
          <instructions>
            Use codebase_search FIRST to understand the relevant parts of the codebase:
@@ -497,7 +519,7 @@ customModes:
          </instructions>
        </step>
 
-       <step number="4">
+       <step number="5">
          <name>Draft Complete Issue Content</name>
          <instructions>
            Create the complete issue body following the exact template structure.
@@ -602,11 +624,17 @@ customModes:
            ## Trade-offs and Risks
 
            [Alternatives considered and potential issues]
+           
+           ## Related Discussions
+           
+           [If any related discussions were found, list them here]
+           - Closes #[discussion number] - [discussion title]
+           - Related to #[discussion number] - [discussion title]
            ```
          </instructions>
        </step>
 
-       <step number="5">
+       <step number="6">
          <name>Review and Confirm with User</name>
          <instructions>
            Present the complete drafted issue to the user for review:
@@ -629,7 +657,7 @@ customModes:
          </instructions>
        </step>
 
-       <step number="6">
+       <step number="7">
          <name>Create GitHub Issue</name>
          <instructions>
            Once user confirms, create the issue using the GitHub MCP tool:
@@ -655,6 +683,7 @@ customModes:
 
      <best_practices>
        - Always search for existing similar issues before creating a new one
+       - Search GitHub Discussions (especially feature-requests category) for related topics
        - Include specific version numbers and environment details
        - Use code blocks with syntax highlighting for code snippets
        - Reference specific files and line numbers from codebase exploration
@@ -663,6 +692,8 @@ customModes:
        - For features, ensure the proposal aligns with project goals
        - Include screenshots or mockups when relevant (ask user to provide)
        - Link to related issues or PRs if found during exploration
+       - Add "Closes #[number]" for discussions that would be fully addressed by the issue
+       - Add "Related to #[number]" for partially related discussions
      </best_practices>
 
      <common_mistakes_to_avoid>
@@ -946,14 +977,23 @@ customModes:
          </step_1_integration>
 
          <step_3_integration>
+           When searching GitHub Discussions:
+           1. Note that GitHub MCP tools don't currently support discussions API
+           2. Instruct user to manually search discussions at:
+              https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests
+           3. Ask user to provide any related discussion numbers they find
+           4. Include these in the "Related Discussions" section of the issue
+         </step_3_integration>
+
+         <step_4_integration>
            During codebase exploration:
            1. Use list_commits to find recent changes to affected files
            2. Use search_code for additional code references
            3. Check list_pull_requests for related PRs
            4. Include findings in the technical context section
-         </step_3_integration>
+         </step_4_integration>
 
-         <step_6_integration>
+         <step_7_integration>
            When creating the issue:
            1. Use create_issue with complete formatted body
            2. Capture the returned issue number