bakers.build

Appearance

How it works ​

One state, one run, one frame. Every step ends with a summary and the next state.

From ticket to finished step ​

  1. A conductor picks up the ticket when the ticket names it, its blockers are closed and a slot is free.
  2. It prepares a workspace on the ticket's branch and starts an agent there.
  3. The agent reads the ticket and every comment, then follows bb-workflow, which routes it to the state's file and the ticket's recipe.
  4. The run does the work and asks you whenever a decision is yours.
  5. It leaves a handoff and a summary, then moves the ticket to the next state. That ends the run; the next state starts a new one.

The ticket's state is the progress. Follow a ticket shows where to watch it.

What your project decides ​

Every run passes the same seven phases: read, provision, work, validate, deliver, outtake, transition. A run is a grid of state × phase: each state's file in bb-workflow has one section per phase, and that section always runs. Three kinds of guidance add slots to the cells:

  • The recipe adds the engineering method to every state, chosen per ticket at qualification (Ticket type, recipe and labels). A slot for one ticket type, such as bug, wins over the general one.
  • A runtime guide, such as bb-runtime-ddev, says how to provision, run, lint, test and log in as a test persona in one technology. It is provisioned only when the work needs it.
  • Your hints in WORKFLOW.md add your runtime, extra skills, checks, merge rules and test users, each under the phase it refines.

The frame, bb-workflow, holds the state files and the rules every run keeps; recipes, guides and hints never own gates, comments or transitions.

Change your way of working with a text edit; no migration needed.

What bakers.build decides ​

The states and transitions themselves belong to the bakers.build server. WORKFLOW.md cannot add or remove states. Changing them is a change to bakers.build itself; see Development.

Check your setup ​

Ask your agent:

text
Check that this project's WORKFLOW.md starts with the bb-workflow entry line, that every skill it names is installed, and name the installed recipes.

A missing recipe, recipe section or required skill, or a state without a state file, stops a run before it changes anything, naming what is missing.

The rules for writing your own recipe or runtime guide are in the skill contract.