🍳 Advanced Recipe Submission #7

[taniandjerry]

🍳 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

• Recipe Reference Guide
• Cookbook Contributing Guide
• Goose Recipes Tutorial (YouTube)
• Existing Recipes

---

🚀 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.

[staru09]

Just to be clear, the blogs should be hosted on a personal website instead of platforms like medium?

[Anudhyan]

Just to be clear, the blogs should be hosted on a personal website instead of platforms like medium?

waiting for response on this @taniandjerry

[taniandjerry]

So sorry, just saw this comment! It can be hosted on a platform like medium or dev.to, just your personal page vs our docs site. Thank you for asking! @staru09 @Anudhyan

[staru09]

.take

[github-actions[bot]]

Thanks for taking this issue! Let us know if you have any questions!

[taniandjerry]

@Better-Boy !

[taniandjerry]

Hi @staru09 , since it's been 3 weeks since you claimed this issue and we are in the last week of Hacktoberfest, I am reopening this issue to give active contributors in this last week the chance to make more submissions. You are welcome to submit to other open issues if they pop up.

[Better-Boy]

.take

[github-actions[bot]]

Thanks for taking this issue! Let us know if you have any questions!