Skip to content

🍳 Advanced Recipe Submission #6 #5123

@taniacryptid

Description

@taniacryptid

🍳 Advanced Recipe Submission

Thanks for contributing to the Goose Cookbook!
This issue represents an Advanced Recipe Slot (8–10 points).

Advanced recipes use 3 or more extensions and/or multiple sub-recipes to orchestrate complex workflows.


βœ… Acceptance Criteria

Your recipe will be accepted if it:

  • Uses 3+ extensions in a single workflow.
  • Optionally (or preferably) includes multiple sub-recipes.
  • Demonstrates orchestration, parameter passing, conditional logic, or parallel execution.
  • Includes required YAML fields: title, description, instructions, and at least one activity.
  • Validates against the Recipe Reference Guide.
  • Has been tested locally in Goose.
  • Follows the Cookbook Contributing Guide.

πŸ“‹ Submission Checklist

Before opening your PR, make sure you've:

  • Chosen a unique and descriptive filename (e.g., code-review-pipeline.yaml).
  • Matched the recipe title to the filename.
  • Confirmed your YAML validates.
  • Listed all extensions and sub-recipes used.
  • Included clear instructions and multiple activities.
  • Verified the recipe works locally in Goose.

✨ Inspiration Examples

(These are just ideas β€” you can submit any real workflow you've used with Goose.)

  • Code review pipeline with sub-recipes (security + quality checks).
  • Smart analyzer that conditionally chooses sub-recipes.
  • Research assistant chaining multiple sources into a report.
  • Project bootstrapper (generate starter templates).
  • Data visualization helper (convert CSV/JSON to charts).

πŸ“š Resources


πŸš€ Next Steps

  1. Claim this slot by commenting .take below.
  2. Fork the repository and create a new branch for your recipe.
  3. Create your recipe file in:
    documentation/src/pages/recipes/data/recipes/
  4. Create a pull request from your fork and reference this issue in the PR description.

πŸŽ‰ Once merged, your recipe will be added to the Goose Cookbook!


πŸ’‘ Tips for Success

  • Think big: combine multiple extensions and/or sub-recipes.
  • Highlight orchestration: chaining, parameter passing, conditional or parallel execution.
  • Test thoroughly β€” advanced workflows are more complex.
  • Document clearly so others can reproduce your results.

Metadata

Metadata

Assignees

Labels

hacktoberfestIssues awarding points for Hacktoberfest 2025!smallWeight label for Hacktoberfest 2025 issues

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions