Ticket type, recipe and labels

The recipe chooses the method, the type chooses its variant, and labels choose the agent and can mirror progress to GitLab.

Field	Set by	Effect
recipe	qualification	the recipe skill that supplies the method for plan, working and review, such as matt for bb-recipe-matt; empty means the installed recipe that declares itself project default
ticket_type	qualification	feature, bug, chore and so on; selects the recipe's slots for that type
labels	you, or qualification	agent choice and plain tags, see below

The fields and their vocabularies are listed under Ticket type, recipe and labels.

Recipes

A recipe is a skill named bb-recipe-<method>, one per engineering method, with one ## bb-state-<state> section per state it refines and ### bb-phase-<phase> slots inside. bakers.build ships bb-recipe-matt, the project default. Qualification reads the descriptions of the installed recipes, picks the one that fits the ask, then a type that recipe declares, and writes both on the ticket. It asks only when the choice is genuinely unclear. A later change follows the bb-scope-change skill.

A run stops before doing any work when the recipe, its section for the current state, or the ticket's type within that recipe is missing. To write your own: Write a recipe.

Labels

Label	Set by	Effect
agent:<alias> or agent:<route>	you, or qualification after you confirm	the coding agent for every state
agent:<alias>@<state> or agent:<route>@<state>	the same	the coding agent for that state only

Anything else is a plain tag for people and filters.

Agent labels

Labels pick from the agent catalog on the machine that runs the ticket. A direct alias beats a route; the full precedence list is in Machines. An unknown or unavailable label warns and falls through. Aliases, routes and defaults are set in Agents and models.

Origin labels

A ticket with a GitLab issue as origin mirrors its progress as a label on that issue: Origin labels.