Step-by-step workflow for creating a new recipe from scratch. Use when the user wants to add a new recipe to the repository. Always starts with a conversation to gather information — never write a recipe without asking first.
Use this when:
Before you start: Read recipe-documentation for the format rules.
Do NOT start writing a recipe file until you have gathered information through conversation.
Recipes are personal. You cannot guess quantities, cooking methods, or serving sizes. ASK FIRST.
Ask the user these questions. Do not skip any unless the answer is already known:
If the user gives quantities in pounds, cups, or ounces:
If the user gives test-batch quantities to scale up:
⚠️ STOP — DO NOT PROCEED TO STEP 2. You need enough information to write the recipe. If you are missing ingredients, quantities, or cooking steps, go back and ask. Do not fill in gaps with guesses.
Use this decision table:
| Situation | Status | Folder |
|---|---|---|
| Recipe is fully tested, quantities are confirmed | stable | Recipes/ |
| Recipe works but needs more testing | beta | Recipes/Beta/ |
| Recipe is incomplete (missing instructions or uncertain quantities) | draft | Recipes/Beta/ |
| Recipe is part of a set (e.g. rub + binder) | Any | Recipes/<Topic>/ |
When in doubt, use beta. It is easier to promote than demote.
Before writing YAML, answer these questions:
branch_group name?volume_alt.related entries.Write out this plan and show it to the user. If you skip this step, you will make structural mistakes.
⚠️ STOP — REVIEW YOUR PLAN BEFORE WRITING ANY YAML. Does the plan match what the user described? If not, revise it. If you are unsure, ask the user to confirm.
Use this template as your starting point: