chore: Simplified the issue templates (#10316)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -2,7 +2,7 @@
 name: Bug report
 about: Create a report to help us improve
 title: ''
-labels: bug
+type: bug
 assignees: ''
 ---
 

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1 @@
 blank_issues_enabled: false
-contact_links:
-  - name: goose Discord discussion
-    url: https://discord.gg/goose-oss
-    about: Please ask and answer questions here.
-  - name: Report a security vulnerability
-    url: https://github.com/aaif-goose/goose/security/policy
-    about: Please report security vulnerabilities here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -2,11 +2,14 @@
 name: Feature request
 about: Suggest an idea for this project
 title: ''
-labels: 'enhancement'
+type: 'feature'
 assignees: ''
 
 ---
 
+**Before opening a feature request**
+Please start a discussion in the [goose-eng Discord channel](https://discord.com/channels/1287729918100246654/1514412780504088677) before creating a feature request or beginning implementation. This helps align on direction before anyone spends time building.
+
 **Please explain the motivation behind the feature request.**
 Does this feature solve a particular problem you have been experiencing? What opportunities or use cases would be unlocked with this feature?
 

.github/ISSUE_TEMPLATE/submit-recipe.yml

@@ -1,99 +0,0 @@
-name: 🧑‍🍳 Submit a recipe to the goose cookbook
-description: Share a reusable goose recipe with the community!
-title: "[Recipe] <your recipe title here>"
-labels: ["recipe submission"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for contributing to the goose cookbook! 🍳  
-        Recipes are reusable sessions created in goose desktop or CLI and shared with the community to help others vibe code faster.
-
-        📌 **How to Submit**
-        - Create your recipe using goose ("Make recipe from this session")
-        - Fill out the YAML below using the format provided
-        - Paste it into the field and submit the issue — we'll review and add it to the cookbook!
-
-        🪄 **What Happens After?**
-        - If accepted, we'll publish your recipe to the [goose recipes cookbook](https://goose-docs.ai/recipes)
-        - Your GitHub handle will be displayed and linked on the recipe card
-        - If the YAML has any issues, goose will comment with validation errors so you can fix and resubmit.
-
-        🧪 **Pro Tip:** You can test your recipe locally in your terminal with:  
-        `goose recipe validate your-recipe.yaml`
-
-  - type: textarea
-    id: recipe-yaml
-    attributes:
-      label: Paste Your Full Recipe YAML Below
-      description: Use the structure below and we'll auto-fill your GitHub handle for `author.contact` after submission.
-      placeholder: |
-        version: "1.0.0"
-        id: clean-up-feature-flag
-        title: Clean Up Feature Flag
-        description: Automatically clean up all references of a fully rolled out feature flag from a codebase and make the new behavior the default.
-        instructions: |
-          Your job is to systematically remove a fully rolled out feature flag and ensure the new behavior is now the default. Use code search tools like ripgrep to identify all references to the flag, clean up definition files, usage sites, tests, and configuration files. Then create a commit and push changes with clear commit messages documenting the flag removal.
-        prompt: |
-          Task: Remove a feature flag that has been fully rolled out, where the feature flag's functionality should become the default behavior.
-
-          Context:
-            Feature flag key: {{ feature_flag_key }}
-            Project: {{ repo_dir }}
-
-          Steps to follow:
-            1. Check out a *new* branch from main or master named using the feature flag key.
-            2. Find the feature flag constant/object that wraps the key.
-            3. Search for all references to the constant/object using ripgrep or equivalent tools.
-            4. Remove all conditional logic and make the new behavior default.
-            5. Remove unused imports, mocks, config, and tests.
-            6. Commit your changes and push the branch.
-            7. Open a GitHub PR.
-
-          Use commit messages like:
-            chore(flag-cleanup): remove <feature_flag_key> flag from codebase
-
-        parameters:
-          - key: feature_flag_key
-            input_type: string
-            requirement: required
-            description: Key of the feature flag
-
-          - key: repo_dir
-            input_type: string
-            requirement: optional
-            default: ./
-            description: Directory of the codebase
-
-        extensions:
-          - type: stdio
-            name: developer
-            cmd: uvx
-            args:
-              - developer-mcp@latest
-            timeout: 300
-            bundled: true
-            description: Access developer tools
-        
-        activities:
-          - Remove feature flag definitions
-          - Clean up feature flag usage sites
-          - Update affected tests
-          - Remove flag configurations
-          - Document flag removal
-    validations:
-      required: true
-
-  - type: markdown
-    attributes:
-      value: |
-        🛠 **Recipe Field Tips**
-        - `version` must be "1.0.0" for now
-        - `id` should be lowercase, hyphenated, and unique (e.g. `my-awesome-recipe`)
-        - `title` is the display name of your recipe
-        - `description` should clearly explain what the recipe does
-        - `instructions` are specific steps goose should follow — supports template variables like `{{ variable_name }}`
-        - `prompt` is the first thing goose sees when the recipe is launched
-        - `parameters` should include required or optional inputs — optional ones must have `default`
-        - `extensions` must follow the full format with `type`, `cmd`, `args`, `timeout`, etc.
-        - `activities` describe the main actions the recipe performs

.github/workflows/autoclose

@@ -1,23 +0,0 @@
-name: Close inactive issues
-on:
-  schedule:
-    - cron: "30 1 * * *"
-
-jobs:
-  close-issues:
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-      pull-requests: write
-    steps:
-      - uses: actions/stale@v9
-        with:
-          days-before-issue-stale: 60
-          days-before-issue-close: 21
-          stale-issue-label: "stale"
-          stale-issue-message: "This issue is stale because it has been open for 30 days with no activity."
-          close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
-          days-before-pr-stale: -1
-          days-before-pr-close: -1
-          any-of-labels: "bug,Bug"
-          repo-token: ${{ secrets.GITHUB_TOKEN }}

CONTRIBUTING.md

@@ -29,16 +29,17 @@ It just means the change was too large for a first contribution. Start with some
 
 ### Issues
 
-If you spot a bug or have a concrete proposal for a feature, please open an issue. This shows the community and
-the maintainers the direction of your thinking.
+If you spot a bug, please open an issue. This shows the community and the maintainers the direction of your
+thinking.
 
 For bugs, describe how to reproduce the problem as clearly as possible. If the issue involves an interaction
 with an LLM, include a diagnostics report if possible.
 
 ### Discussions
 
-If you have an idea but are not yet sure how it should work, open a discussion instead. Discussions are a good
-place to explore design questions, alternatives, and whether something fits the goals of the project.
+Before opening a feature request or beginning implementation, please start with a discussion in the
+[goose-eng Discord channel](https://discord.com/channels/1287729918100246654/1514412780504088677). Discussions
+are a good place to explore design questions, alternatives, and whether something fits the goals of the project.
 
 If a change is large or touches multiple parts of the codebase, please start with a discussion before opening a PR.
 This helps us align on direction before you spend time implementing something.