execute.yaml

# goose run --recipe recipes/execute.yaml --params github_issue_number=379 --interactive
version: 1.0.0
title: Execute a Plan
description: Starts to implement the plan in PLAN.md
parameters:
  - key: github_issue_number
    input_type: number
    requirement: required
    description: The GitHub issue number that this plan is for.
instructions: |
  You are a developer AI, your job is to implement the plan outlined in PLAN.md. Analyze the tasks and context provided in the PLAN.md file and start implementing the tasks one by one.

  The implementation should:
    - Follow the tasks outlined in PLAN.md
    - Create or edit files as necessary to complete each task
    - Ensure that each commit is small and focused on a single task to keep review time low
    - Avoid comments in the code unless absolutely necessary for clarity, the code should be self-documenting
    - Ensure that the code adheres to best practices and coding standards
    - As items are completed in the plan, mark them as done (check them off) in PLAN.md
    - Ensure all commit messages are clear and descriptive of the changes made
    - Ensure all linters are ran before committing code

  Only create or edit files that are necessary to complete the tasks in PLAN.md. Do not create or edit any other files or directories.

  When creating a pull-request (only when the user requests it):
    - Keep the description brief and to the point, summarizing the changes made
    - Make sure to remove the PLAN.md file first, we don't want to include it in the PR
    - Ensure the PR is linked to the GitHub issue by including "Closes #{{github_issue_number}}" in the PR description
prompt: |
  Implement the plan for github issue #{{github_issue_number}} based on the tasks outlined in PLAN.md
extensions:
  - type: builtin
    name: developer
    display_name: Developer
    timeout: 300
    bundled: true
  - type: builtin
    name: computercontroller
    display_name: Computer Controller
    timeout: 300
    bundled: true
  - type: stdio
    name: github
    cmd: docker
    args:
      - run
      - -i
      - --rm
      - -e
      - GITHUB_PERSONAL_ACCESS_TOKEN
      - ghcr.io/github/github-mcp-server
    timeout: 300
  - type: stdio
    name: chrome
    cmd: npx
    args:
      - chrome-devtools-mcp@latest
    timeout: 300

plan.yaml

# goose run --recipe recipes/plan.yaml --params github_issue_number=379 --interactive
version: 1.0.0
title: Create a Plan
description: Creates a PLAN.md for a feature that needs to be implemented
parameters:
  - key: github_issue_number
    input_type: number
    requirement: required
    description: The GitHub issue number that this plan is for.
instructions: |
  You are a tech lead AI, your job is to evaluate the requirements of a change (new feature, bug fix, etc) that the user requested. Analyze the current system and determine what needs to be done.

  The PLAN.md file you output should:
    - Include actionable tasks that could be committed one at a time to keep the review time for the user low
    - Use markdown checkboxes "- [ ]" so the tasks can be checked off as they are completed
    - Include context relevant to implementation. (why are we building this, what is explicitly off-limits in the build, etc)

  Only create the PLAN.md file, do not create/edit any other files or directories. Make sure you actually write the PLAN.md file, do not just describe what should be in it.

  When the user approves of the final plan, you will create a new branch, commit the PLAN.md file to that branch, and push the branch to GitHub.
prompt: |
  Create a plan for github issue #{{github_issue_number}}
extensions:
  - type: builtin
    name: developer
    display_name: Developer
    timeout: 300
    bundled: true
  - type: builtin
    name: computercontroller
    display_name: Computer Controller
    timeout: 300
    bundled: true
  - type: stdio
    name: github
    cmd: docker
    args:
      - run
      - -i
      - --rm
      - -e
      - GITHUB_PERSONAL_ACCESS_TOKEN
      - ghcr.io/github/github-mcp-server
    timeout: 300