WorkflowsSection 5 of 13 · 3 workflows
Verification
Planning tells the agent what to build. This section is about how it proves the work is right, so that "done" is a result the agent measured and not a claim it made.
- 6 min readThe Browser Verification LoopThe highest-leverage change a Frontend team can make to its agent setup. Until the agent can open the page it just built, "done" only ever means "it compiled", and you are the verification loop.Read
- 9 min readGolden-PR EvalsEvery team has an opinion about whether their agent setup is any good. Almost nobody has a number. An eval suite built from your own merged pull requests turns "the agent is doing great" into a score you can regress against, and it is the only honest way to compare a model, a CLAUDE.md rewrite or a new skill.Read
- 6 min readEvals for the LLM Features You ShipA feature that calls a model does not give the same answer twice, so a green unit test says very little about it. The eval set that protects it cannot be written in a planning doc. It gets harvested from what the feature actually did to real users.Read