Appearance
Skills & Workflows
Your project decides how agents work. bakers.build keeps every ticket on track.
Each ticket follows a workflow: a fixed series of states such as plan, working and review. In each state, one skill tells the agent what to do; in the work states that is the ticket's recipe, your engineering method. The WORKFLOW.md in your repository adds your runtime, extra skills and checks.
- How it works: from a ticket to a finished step.
- Configure your workflow: shape
WORKFLOW.mdfor your project. - Workflows and states: what happens in each state.
- Ticket type, recipe and labels: the method, its variant and the agent for a ticket.
Ask your agent
Explain which state file and recipe run each state of this project's workflow, and check that every skill its WORKFLOW.md names is installed.